From: Daniel Jacobowitz <drow@false.org>
To: Mathieu Lacage <mathieu.lacage@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: how to make gdb happy with my linkmap
Date: Mon, 05 Jan 2009 17:13:00 -0000 [thread overview]
Message-ID: <20090105171315.GA31779@caradoc.them.org> (raw)
In-Reply-To: <74fef6df0901050658g6c279a3ah321c7c6e30630475@mail.gmail.com>
On Mon, Jan 05, 2009 at 03:58:39PM +0100, Mathieu Lacage wrote:
> What I find weird is:
> 1) mathieu@mathieu-boulot:~/code/elf-loader$ readelf -s ./ldso |grep stage1
> 225: 00000932 135 FUNC GLOBAL HIDDEN 6 stage1
> mathieu@mathieu-boulot:~/code/elf-loader$ readelf -l ./ldso
>
> Elf file type is DYN (Shared object file)
> Entry point 0x932
> There are 6 program headers, starting at offset 52
> [...]
>
> i.e., stage1 is located at offset 0x932, and not 0x944 so, I can't
> figure out where the 0x944 displayed by gdb is coming from.
That's prologue skipping; it's just walking past the frame setup.
This helps GDB to display function arguments correctly.
> I also
> find it surprising that gdb is actually trying to set a breakpoint at
> address 0x944: this is a pie binary so, gdb should know that the
> address will be known only once the program is run....
This is the same problem as PIE support. Ubuntu and Fedora carry some
patches to improve PIE support; I think that Jan K. was talking about
merging those at some point. I haven't looked at them in years.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-01-05 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:42 Mathieu Lacage
2008-12-18 21:49 ` Daniel Jacobowitz
2008-12-18 22:03 ` Mathieu Lacage
2008-12-18 22:10 ` Daniel Jacobowitz
2008-12-26 10:40 ` Mathieu Lacage
2008-12-26 12:54 ` Daniel Jacobowitz
2009-01-05 14:58 ` Mathieu Lacage
2009-01-05 17:13 ` Daniel Jacobowitz [this message]
2009-01-07 16:46 ` Doug Evans
2009-01-12 15:08 ` Mathieu Lacage
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=20090105171315.GA31779@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mathieu.lacage@gmail.com \
/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