From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot malloc implementation on arm - problem after relocation
Date: Wed, 7 Oct 2015 19:38:21 +0200 [thread overview]
Message-ID: <5615588D.2050808@suse.de> (raw)
In-Reply-To: <CABc_YGALMrb7k23o3mN0VxUJ2t8pWmxtu6j_6BR++LFGnM9XzA@mail.gmail.com>
Hi Marcin,
Am 07.10.2015 um 15:58 schrieb Marcin Krzemi?ski:
> Since I use qemu it
> is very hard to debug with gdb u-boot after relocation( or I do not know
> how to do it), so I am almost blind.
QEMU has a built-in gdb stub that you can just connect to as gdb remote
target, similar to how you would connect to a JTAG adapter's gdb server.
See documentation of qemu-system-arm -gdb and -s options.
It should behave the same as with a physical remote target, otherwise
please report to qemu-devel or a suitable bug tracker.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2015-10-07 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 13:58 [U-Boot] U-Boot malloc implementation on arm - problem after relocation Marcin Krzemiński
2015-10-07 17:38 ` Andreas Färber [this message]
2015-10-07 18:25 ` mar.krzeminski
2015-10-08 13:29 ` Marcin Krzemiński
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5615588D.2050808@suse.de \
--to=afaerber@suse.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox