Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Gary Benson <gbenson@redhat.com>
Subject: Re: [RFA] Improved linker-debugger interface
Date: Mon, 07 May 2012 20:27:00 -0000	[thread overview]
Message-ID: <87r4uvwxcg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120507165648.GA22472@host2.jankratochvil.net> (Jan	Kratochvil's message of "Mon, 7 May 2012 18:56:48 +0200")

Gary> My current setup has a probe everywhere _dl_debug_state is called,

Jan> I believe you should submit the STAP (SystemTap) probes patch to
Jan> GNU libc along.  I do not see too great to patch GNU gdb for a libc
Jan> feature not in GNU libc.

I don't see that as such a big deal.  We have patches in gdb for all
kinds of system- and compiler-specific behavior.  At least in this case
the patches in question are public and free software.

I do agree that we should make another attempt to get the probes
upstream; I just don't think success at that should be a precondition
for this patch.

FWIW, we already have support for the glibc longjmp probes in the tree
now.

Tom


  parent reply	other threads:[~2012-05-07 20:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 15:22 Gary Benson
2012-05-05  4:39 ` Sergio Durigan Junior
2012-05-05  6:03   ` Jan Kratochvil
2012-05-05  6:11     ` Sergio Durigan Junior
2012-05-05  6:23       ` Jan Kratochvil
2012-05-07 16:57 ` Jan Kratochvil
2012-05-07 17:51   ` Sergio Durigan Junior
2012-05-07 20:27   ` Tom Tromey [this message]
2012-05-07 21:32     ` Mark Kettenis
2012-05-07 21:44       ` Jan Kratochvil
2012-05-08  5:45       ` Sergio Durigan Junior
2012-05-08 13:37       ` Tom Tromey
2012-05-09  8:12         ` Mark Kettenis
2012-05-09 15:57           ` 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=87r4uvwxcg.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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