public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	Gary Benson <gbenson@redhat.com>
Subject: Re: [PATCH] Remove support for "rtld_" prefix on solib-svr4 probes
Date: Thu, 25 Sep 2014 21:53:00 -0000	[thread overview]
Message-ID: <87eguzfju7.fsf@redhat.com> (raw)
In-Reply-To: <54248CD1.8000801@redhat.com> (Pedro Alves's message of "Thu, 25	Sep 2014 22:44:49 +0100")

On Thursday, September 25 2014, Pedro Alves wrote:

> There's the system GDB, that is usually maintained by the
> distro, but then it's quite often the case that people build
> and ship their own tools on top of the distro, bypassing the
> system tools.

Yeah.

> I tend to view supporting older-ish distros that people might
> still be using like the proprietary OSs we "support" (in a sense).
> I think that just as we'd accept a patch that makes GDB work better
> on Windows 7 OOTB (e.g., to work around some debug API issue), even
> though there's already Windows 8 out there, I think patches that make
> GDB work better OOTB on a bit older (but still in use) distros are
> fine, as long as they don't get in the way of progress and don't
> impose a big maintenance burden.

Heh, in my personal opinion GDB should not support proprietary OSes
OOTB.  But I certainly don't want to start a flamewar.

As for support a bit older distro that might still be out there, I
totally agree with you.  The problem is that we (as a community) don't
usually track those things very well, and code here tends to be forgot
until someone stumbles on it because of some bug...

> IMHO, there's no harm in leaving this particular bit in
> a while longer.

Me too, definitely, but there's the issue I raised in the sentence
above...

> But I certainly won't cry over this.  I'm not personally affected.
> If others are fine with yanking this out, I'll be fine with it too.

Thanks.  I will wait a few more days, and if nobody else objects, I will
go ahead and push this patch in.

BTW, if I push this in, I believe my other patch to adjust the testsuite
becomes obvious, right?  (Assuming that the test is indeed needed, as
you already pointed out).

Thanks,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

  reply	other threads:[~2014-09-25 21:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 18:03 [RFA] Fix PR gdb/17016: Expect for probe "map_complete" instead of "rtld_map_complete" Sergio Durigan Junior
2014-09-25  9:41 ` Gary Benson
2014-09-25 10:38 ` Pedro Alves
2014-09-25 20:47   ` [PATCH] Remove support for "rtld_" prefix on solib-svr4 probes (was: Re: [RFA] Fix PR gdb/17016: Expect for probe "map_complete" instead of "rtld_map_complete") Sergio Durigan Junior
2014-09-25 21:13     ` [PATCH] Remove support for "rtld_" prefix on solib-svr4 probes Pedro Alves
2014-09-25 21:23       ` Sergio Durigan Junior
2014-09-25 21:44         ` Pedro Alves
2014-09-25 21:53           ` Sergio Durigan Junior [this message]
2014-09-25 22:07             ` Pedro Alves
2014-09-25 22:21               ` Sergio Durigan Junior
2014-09-26  8:23                 ` Gary Benson

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=87eguzfju7.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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).