Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@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:44:00 -0000	[thread overview]
Message-ID: <54248CD1.8000801@redhat.com> (raw)
In-Reply-To: <87r3yzfl86.fsf@redhat.com>

On 09/25/2014 10:23 PM, Sergio Durigan Junior wrote:
> On Thursday, September 25 2014, Pedro Alves wrote:
> 
>> There's RHEL (at least, per the comment) 6.4 too, which isn't EOL'ed,
>> though.  It's reasonable to expect that people may still want to
>> build/test upstream gdb on those?
> 
> Damn, I forgot to talk about RHEL.
> 
> But yeah, RHEL-6.x is not EOL'ed, but the GDB that comes with it is from
> Red Hat as well, and contains all the necessary patches to deal with
> whatever "internal idiosyncrasy" that it may need.  OTOH, I know Gary
> has been using RHEL-6.5 to test his upstream patches, so to answer your
> question, it is still possible that people may still want to buid/test
> upstream GDB there.
> 
> My opinion is that we shouldn't need to worry about internals of each
> distro (I know we *have to do that* sometimes, but that's not an
> excuse), so I still hold the cleanup patch for approval :-).

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.

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.

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

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,
Pedro Alves


  reply	other threads:[~2014-09-25 21:44 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 [this message]
2014-09-25 21:53           ` Sergio Durigan Junior
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=54248CD1.8000801@redhat.com \
    --to=palves@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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