From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>,
Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: remove "info dll" alias to "info sharedlibraries"?
Date: Mon, 05 Jan 2015 17:35:00 -0000 [thread overview]
Message-ID: <54AACB30.2020909@redhat.com> (raw)
In-Reply-To: <20141231073147.GB5445@adacore.com>
On 12/31/2014 07:31 AM, Joel Brobecker wrote:
>> What's the basis for believing that "we've already trained the users"?
>
> We've made the "dll-*" commands deprecated, and now just removed them.
>
>> With a little poking around the net, I did notice a couple examples
>> where people were reporting "info dll" results. But in practice I
>> suspect that most GDB-using Windows developers are working on multiple
>> platforms, and they're likely to prefer commands that work everywhere.
>
> I only found a couple of instances myself, from 2005 and 2008.
>
>> On the other hand, "info dll" has been documented for a long time,
>> and is only one line of extra code - seems like more work to remove
>> than to leave it alone.
>>
>> I do think we can dump the hook and just use add_info_alias. I don't
>> remember exactly why the hook seemed necessary in the first place, but
>> the timing suggests I added it for gdbtk or MPW (or both. :-) ).
>
> But I agree it's been documented for a long time. Let's see if I
> can just keep the alias without the hook (on my next rainy day :-)).
If it stays, it's best to move it to windows-tdep.c so that it's
available when cross debugging Windows from a non-Windows host too.
Or to solib.c, even.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-01-05 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 7:54 Joel Brobecker
2014-12-30 23:22 ` Stan Shebs
2014-12-31 7:31 ` Joel Brobecker
2015-01-05 17:35 ` Pedro Alves [this message]
2015-01-05 17:44 ` Joel Brobecker
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=54AACB30.2020909@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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).