Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org,
	gbenson@redhat.com
Subject: Re: [RFA] Improved linker-debugger interface
Date: Mon, 07 May 2012 21:32:00 -0000	[thread overview]
Message-ID: <201205072131.q47LVjTN014466@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <87r4uvwxcg.fsf@fleche.redhat.com> (message from Tom Tromey on	Mon, 07 May 2012 14:27:27 -0600)

> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 07 May 2012 14:27:27 -0600
> 
> 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 think this is a big deal.  We can't just add support for every
feature that looks neat into GDB.  In the long run, that will lead to
an unmaintainable codebase.  

I'm pretty annoyed by the whole SystemTap thing.  You presented this
as being something pretty generic.  But it turns out this is not only
Linux-specfic, but pretty much a completely RedHat-specific thing it
seems.  And I think I've figured out why: SystemTap relies on utrace,
which is not present in the official Linux kernel source tree.  And as
far as I can see it will remain that way in the near future.  So
unless you are running RedHat Linux, you'll not only need to build a
patched glibc, but you also need to build a patched kernel to be able
to use these new SystemTap probes.  Not many people will do that!

Having the basic SystemTap support in GDB is fine.  But depending on
it to fix issues with core GDB functionality like the ability to debug
shared libraries is a different matter.  It means that people using
RedHat Linux, almost certainly including any RedHat engineers
contributing here will no longer test the codepaths that don't rely on
SystemTap.  And people on other Linux variants will never test the
codepaths that rely on SystemTap.  That'll inevitably lead to more
breakage.

> 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.

If you ask me, having utrace in the official Linux kernel should be a
precondition for this patch as well.

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

In the glibc tree?  Or in the GDB tree?  If these probes are not
present in the official glibc tree, the support for those particular
probes should not be in the official GDB tree either.


  reply	other threads:[~2012-05-07 21:32 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
2012-05-07 21:32     ` Mark Kettenis [this message]
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=201205072131.q47LVjTN014466@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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