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 22:21:00 -0000 [thread overview]
Message-ID: <87vbobe3yu.fsf@redhat.com> (raw)
In-Reply-To: <54249203.3030607@redhat.com> (Pedro Alves's message of "Thu, 25 Sep 2014 23:06:59 +0100")
On Thursday, September 25 2014, Pedro Alves wrote:
> 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!
Haha, thanks for sharing your experience :-).
> 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.
Yeah, that is a fair point, and it is very valid when we talk about
things that might make GDB break badly when removed. But in this case,
we are talking about a very specific Fedora/RHEL thing, which is itself
intended to improve something (i.e., GDB will still work without it on
old Fedora/RHEL systems), so I think most of the concerns don't apply
here.
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2014-09-25 22:21 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
2014-09-25 22:21 ` Sergio Durigan Junior [this message]
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=87vbobe3yu.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).