public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: add "set debug solib" and use it
Date: Mon, 21 Nov 2022 15:24:36 -0500	[thread overview]
Message-ID: <fdf7fad3-8d0c-b857-9d61-0ac3308ba1ff@polymtl.ca> (raw)
In-Reply-To: <65327b23-1e3c-b9c9-6e42-f8c039905bdf@polymtl.ca>



On 11/21/22 15:24, Simon Marchi wrote:
> 
> 
> On 11/21/22 15:19, Eli Zaretskii wrote:
>>> Date: Mon, 21 Nov 2022 15:02:08 -0500
>>> Cc: gdb-patches@sourceware.org
>>> From: Simon Marchi <simon.marchi@polymtl.ca>
>>>
>>>> Not sure I understand: we already have "set debug aix-solib" and "set debug
>>>> solib-frv".  So this is going to be "set debug svr4-solib"?  Or do you mean
>>>> to make a single "set debug solib" command for all platforms?
>>>
>>> The new command was intended to be used by all solib implementations,
>>> but I missed the existing commands you pointed out.  I think it would be
>>> fine to have a single knob for all solib implementations.  In general,
>>> only one solib implementation will be used at any given time.
>>>
>>> If you agree, I would remove the two existing commands in favor of the
>>> new "set debug solib", and then add my solib-svr4 changes.
>>
>> I have no use for those two commands, but I guess users of AIX and FRV do?
>> Can we just delete the commands from under their feet?
> 
> I tend to view "set debug" commands, as internal commands (maybe they
> should be maintenance commands, really), I wouldn't feel bad to just
> remove them.  Or we could keep them as deprecated aliases of the new
> command.  Or, I could just add "set debug solib-svr", if that makes

solib-svr4, sorry.

Simon

  reply	other threads:[~2022-11-21 20:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 19:36 Simon Marchi
2022-11-21 19:56 ` Eli Zaretskii
2022-11-21 20:02   ` Simon Marchi
2022-11-21 20:19     ` Eli Zaretskii
2022-11-21 20:24       ` Simon Marchi
2022-11-21 20:24         ` Simon Marchi [this message]
2022-11-28 15:27         ` Tom Tromey
2022-11-28 16:57   ` Simon Marchi

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=fdf7fad3-8d0c-b857-9d61-0ac3308ba1ff@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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).