From: Daniel Jacobowitz <drow@false.org>
To: Torsten Mohr <tmohr@s.netic.de>
Cc: newlib@sourceware.org, gdb@sourceware.org,
Jeff Johnston <jjohnstn@redhat.com>
Subject: Re: malloc() never returns
Date: Fri, 09 Jun 2006 13:51:00 -0000 [thread overview]
Message-ID: <20060608231018.GA5183@nevyn.them.org> (raw)
In-Reply-To: <200606082341.12598.tmohr@s.netic.de>
On Thu, Jun 08, 2006 at 11:41:12PM +0200, Torsten Mohr wrote:
> So is it possible that GDB loads the sections in the ELF file to the
> VMA and not to the LMA?
That is correct.
> Is there a standard solution to this standard problem?
No, I don't think there is. However, people have started to mention
this as a problem more frequently in the last few months. Maybe it's
time for "load" to grow an option to use LMA.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-06-08 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606081246.20231.tmohr@s.netic.de>
[not found] ` <44886BBF.1030404@redhat.com>
2006-06-08 21:50 ` Torsten Mohr
2006-06-09 13:51 ` Daniel Jacobowitz [this message]
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=20060608231018.GA5183@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jjohnstn@redhat.com \
--cc=newlib@sourceware.org \
--cc=tmohr@s.netic.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