From: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [7.0] PR/9723: gdb breakpoints silently fail on PIE binaries
Date: Sat, 25 Jul 2009 02:11:00 -0000 [thread overview]
Message-ID: <200907242312.42358.thiago.bauermann@gmail.com> (raw)
In-Reply-To: <8ac60eac0907192113s54f996a7m2fac203e07687272@mail.gmail.com>
Em Segunda-feira 20 Julho 2009 01:13:00 Paul Pluzhnikov escreveu:
> On Sun, Jul 19, 2009 at 6:57 PM, Thiago Jung
>
> Bauermann<thiago.bauermann@gmail.com> wrote:
> > All this to say: can somebody save me some research time and tell in high
> > level how can I recognize from looking at an ELF file that I'm dealing
> > with a PIE binary (NOT a PIC library, of course)? Something like "see if
> > the frob bit in the bozo section is set") is enough, I can go from there.
>
> Elf*_Ehdr.e_type == ET_DYN for the main executable?
>
> Elf*_Phdr.p_vaddr == 0 for the first PT_LOAD segment?
> [This one is only true for non-prelinked -pie executable.]
Great, thanks for the tip. Since nobody jumped into discussion, I assume any
of those ways will work and have no known side-effect or false
positive/negative. We'll see. :-)
Now I have this issue, I'd like to ask people's opinion about it: by design
(or defect?) the BFD library is a PITA to access the program header. I feel
very tempted to use elf32.h and elf64.h directly in order to check that field.
My only worry is that a cross-debugging session with a win32 gdb and a linux
remote target would not be possible, unless windows includes such sysv elf
headers too (perhaps it does?).
Do you have an opinion?
--
[]'s
Thiago Jung Bauermann
next prev parent reply other threads:[~2009-07-25 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 1:55 Thiago Jung Bauermann
2009-07-20 4:13 ` Paul Pluzhnikov
2009-07-25 2:11 ` Thiago Jung Bauermann [this message]
2009-07-25 2:26 ` Daniel Jacobowitz
2009-07-25 9:56 ` Mark Kettenis
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=200907242312.42358.thiago.bauermann@gmail.com \
--to=thiago.bauermann@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.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