From: Roland McGrath <roland@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: hook to run on attach/exec?
Date: Thu, 29 Jan 2004 04:08:00 -0000 [thread overview]
Message-ID: <200401290408.i0T48VrC001340@magilla.sf.frob.com> (raw)
I read someone mention somewhere recently that a new hook might be in the
works to be the spot where PIE support would figure out where the
executable got loaded. Can someone give me the skinny?
For vsyscall DSO detection, the hook I need goes at the same place, I
think. That is, a spot that gets run after an inferior execs (from "run"
or otherwise, skipping first "run" exec for the shell of course) or when
gdb attaches to an inferior or to a core dump image; i.e., whenever the
inferior's address space is freshly made or presumed to be. Those are the
times you need to figure out where a PIE actually resides in memory, and
also the times you need to figure out where a system-supplied DSO is.
Last time I was looking into the vsyscall DSO support, it seemed like there
was no precisely appropriate hook already. But I didn't know exactly what
to do about adding one. Is my life easier now?
Thanks,
Roland
next reply other threads:[~2004-01-29 4:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 4:08 Roland McGrath [this message]
2004-01-29 4:13 ` Daniel Jacobowitz
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=200401290408.i0T48VrC001340@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=gdb-patches@sources.redhat.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