public inbox for gdb-patches@sourceware.org
 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:13:00 -0000	[thread overview]
Message-ID: <54248579.8030606@redhat.com> (raw)
In-Reply-To: <87bnq3h1gf.fsf_-_@redhat.com>

On 09/25/2014 09:47 PM, Sergio Durigan Junior wrote:
> Thanks for the review.
> 
> On Thursday, September 25 2014, Pedro Alves wrote:
> 
>> Well, AFAICS, upstream GDB still supports F17's probes.  See
>> svr4_create_solib_event_breakpoints:
>>
>> 	  memset (probes, 0, sizeof (probes));
>> 	  for (i = 0; i < NUM_PROBES; i++)
>> 	    {
>> 	      const char *name = probe_info[i].name;
>> 	      struct probe *p;
>> 	      char buf[32];
>>
>> 	      /* Fedora 17 and Red Hat Enterprise Linux 6.2-6.4
>> 		 shipped with an early version of the probes code in
>> 		 which the probes' names were prefixed with "rtld_"
>> 		 and the "map_failed" probe did not exist.  The
>> 		 locations of the probes are otherwise the same, so
>> 		 we check for probes with prefixed names if probes
>> 		 with unprefixed names are not present.  */
>> 	      if (with_prefix)
>> 		{
>> 		  xsnprintf (buf, sizeof (buf), "rtld_%s", name);
>> 		  name = buf;
>> 		}
>>
>> 	      probes[i]
> 
> Indeed it does, thanks for catching this.
> 
>> So it seems to me the test should cope with both variants.
> 
> Or maybe we should simplify this code and remove this support.
> 
> Really, Fedora 17 was EOL'ed more than 1 year ago:
> 
>   <https://lists.fedoraproject.org/pipermail/announce/2013-July/003177.html>
> 
> And we are already on Fedora 20, moving towards Fedora 21.  Also, this
> code was needed because a patch present in Fedora 17's glibc, so I think
> it is fair to leave this to be handled by Fedora GDB if needed (but it
> won't be, because the upstream glibc patches already made into Fedora
> too).

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?

Thanks,
Pedro Alves

  reply	other threads:[~2014-09-25 21:13 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     ` Pedro Alves [this message]
2014-09-25 21:23       ` [PATCH] Remove support for "rtld_" prefix on solib-svr4 probes Sergio Durigan Junior
2014-09-25 21:44         ` Pedro Alves
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=54248579.8030606@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).