From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH] gdb: add "set debug solib" and use it
Date: Mon, 28 Nov 2022 08:27:43 -0700 [thread overview]
Message-ID: <87k03fp09c.fsf@tromey.com> (raw)
In-Reply-To: <65327b23-1e3c-b9c9-6e42-f8c039905bdf@polymtl.ca> (Simon Marchi via Gdb-patches's message of "Mon, 21 Nov 2022 15:24:06 -0500")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> I tend to view "set debug" commands, as internal commands (maybe they
Simon> should be maintenance commands, really), I wouldn't feel bad to just
Simon> remove them.
Yes, I think that's fine.
And I also agree that we should probably move these to "maint" someday.
Tom
next prev parent reply other threads:[~2022-11-28 15:27 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
2022-11-28 15:27 ` Tom Tromey [this message]
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=87k03fp09c.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).