From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: archer@sourceware.org
Subject: Re: Improved linker-debugger interface
Date: Tue, 31 May 2011 20:41:00 -0000 [thread overview]
Message-ID: <BANLkTinytKxuubfkVOcvdKiiczUrmvkyLDOeof3sPKg1Qycx7Q@mail.gmail.com> (raw)
In-Reply-To: <m3ipsqr6uh.fsf@fleche.redhat.com>
On Tue, May 31, 2011 at 12:46 PM, Tom Tromey <tromey@redhat.com> wrote:
> Gary> Is it possible for in-process debuggers to locate SystemTap probes?
>
> The probes are described in an non-allocated section, so IIUC they
> aren't mapped by ld.so. I guess a program could examine the executables
> and libraries it uses and map them itself.
Yes, the in-process debugger usually will try to open the ELF file (e.g. to
get to .debug_*, etc.), so it looks like locating the SystemTap probes
would work fine.
On Tue, May 31, 2011 at 9:24 AM, Gary Benson <gbenson@redhat.com> wrote:
> Is making _dl_debug_state_extended an indirect call the only non-hacky
> way to allow in-process debuggers to get these notifications, or are
> there other possibilities?
Once the probe is located, the in-process debugger still has a problem:
not enough space to place a patch on (in-process debugger can not put a
breakpoint on the one instruction that is available).
Making the probes wider would be ideal.
> By the way, although _dl_debug_state compiles to a single ret, I think
> function entries are aligned so you might get a few more bytes to work
> with on some platforms.
I believe I've seen some *86 builds of glibc which did not align functions.
--
Paul Pluzhnikov
next prev parent reply other threads:[~2011-05-31 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 15:37 Gary Benson
2011-05-25 18:21 ` Tom Tromey
2011-05-26 17:02 ` Gary Benson
2011-05-26 17:25 ` Tom Tromey
2011-05-26 17:37 ` Paul Pluzhnikov
2011-05-26 17:47 ` Tom Tromey
2011-05-26 21:07 ` Tom Tromey
2011-05-31 16:25 ` Gary Benson
2011-05-31 19:46 ` Tom Tromey
2011-05-31 20:41 ` Paul Pluzhnikov [this message]
2011-05-31 20:46 ` Tom Tromey
2011-05-31 21:05 ` Paul Pluzhnikov
2011-06-02 23:56 ` Tom Tromey
2011-06-07 16:58 ` Jan Kratochvil
2011-06-08 10:56 ` Gary Benson
2011-06-01 1:24 Frank Ch. Eigler
2011-06-02 23:56 ` Tom Tromey
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=BANLkTinytKxuubfkVOcvdKiiczUrmvkyLDOeof3sPKg1Qycx7Q@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=archer@sourceware.org \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).