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 22:07:00 -0000	[thread overview]
Message-ID: <54249203.3030607@redhat.com> (raw)
In-Reply-To: <87eguzfju7.fsf@redhat.com>

On 09/25/2014 10:53 PM, Sergio Durigan Junior wrote:

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

I don't either.  But I'd rather a user stuck on such a OS be able to
use a free debugger, than drive him towards a proprietary debugger.
That's part of how I got involved into GDB in the first place.  I was
forced to used Windows at work.  I worked around that by using Cygwin,
to be able to use the free tools I preferred.  At the same time
I needed to build a tool that would run on Windows CE.  So I worked on
the GNU toolchain in order to target that OS.  Then I wanted to make Cygwin
GDB better too, because it was similar to CE, and I was using it
at work too.  And then somehow I ended up working on GDB full
time.  :-P  It's a trap, I tells ya!

The real point was that the user building GDB may have no control
over the system bits of the distro it is building GDB for (in this
case glibc's loader), just like when building for a proprietary OS,
even though GNU/Linux distros are based (mostly) on free sources.

Thanks,
Pedro Alves

  reply	other threads:[~2014-09-25 22:07 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
2014-09-25 22:07             ` Pedro Alves [this message]
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=54249203.3030607@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).