public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: archer@sourceware.org
Subject: Re: Improved linker-debugger interface
Date: Thu, 26 May 2011 17:47:00 -0000	[thread overview]
Message-ID: <m3d3j5z754.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BANLkTimn8XXk3nf86zh4ELtV_-FDYugsuQ@mail.gmail.com> (Paul Pluzhnikov's message of "Thu, 26 May 2011 10:36:42 -0700")

Paul> 1. Stripped binaries.

Paul>    There is a DT_DEBUG entry pointing to _dl_debug_state (set by ld-linux)

Paul>    You might want to have a new dynamic tag, pointing to
Paul>    _dl_debug_state_extended(), so the debugger would be able to track
Paul>    shared libs using the new mechanism even when everything is stripped.

SystemTap probes aren't stripped, so I think this should work fine.
This is one of the big plusses (from my POV) of using probes, and it is
why we introduced probes into longjmp and the exception unwinder too --
it lets gdb features work even when the user hasn't installed debuginfo
for glibc and/or libgcc.

This stuff is in F15.  It wasn't accepted into glibc mainline.

Paul> 2. In-process debuggers.

Paul>    B) compiles down to a single 'ret', so there is no way to place a patch
Paul>    on top of it.

Right now a SystemTap probe is a single nop, so probably no joy there.
We have talked about making it a wider nop, though, to facilitate this
kind of patching, primarily I think by LTTng.  What do you think of
this?

Paul>    Perhaps co-operation with "in-process" debuggers would be more
Paul>    acceptable for a new interface?

It is fine by me.

Tom

  reply	other threads:[~2011-05-26 17:47 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 [this message]
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
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=m3d3j5z754.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).