From: Andrew Burgess <aburgess@redhat.com>
To: Guinevere Larsen <guinevere@redhat.com>,
Ciaran Woodward <ciaranwoodward@xmos.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 2/2] gdb: add warning when no native target is available
Date: Mon, 12 Jan 2026 15:33:44 +0000 [thread overview]
Message-ID: <878qe2vo9z.fsf@redhat.com> (raw)
In-Reply-To: <c9509cab-8de1-4870-b3f6-0ea106b88d6c@redhat.com>
Guinevere Larsen <guinevere@redhat.com> writes:
> On 1/9/26 11:16 AM, Ciaran Woodward wrote:
>>> Hmmm, that's a good point. I think I can add a switch to this, to be
>>> added to the gdbinit (or maybe gdbearlyinit), will cook a v3 in a moment.
>> Would you object to making it configure-time, or would that break your
>> intended use case?
Currently, if a user tries to 'run' when there's no native target
support, GDB gives an error like:
Don't know how to run. Try "help target".
Would your new text be better emitted around the time this error is
produced? The actual output of 'help target' is pretty unhelpful for a
confused user I think, it's mostly just a list of the various target
sub-commands. But there is some introductory text at the top, maybe we
could do something smart and inject your new warning there for GDB's
without a native target?
Both of these would defer the additional text to the point where the
user has tried to do the wrong thing, at which point, printing more text
is OK.
Just a thought.
Thanks,
Andrew
next prev parent reply other threads:[~2026-01-12 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 11:56 [PATCH v2 0/2] Add warning if the native target is not supported Guinevere Larsen
2026-01-09 11:56 ` [PATCH v2 1/2] gdb: improve help text for set commands with limited options Guinevere Larsen
2026-01-12 15:35 ` Andrew Burgess
2026-01-09 11:56 ` [PATCH v2 2/2] gdb: add warning when no native target is available Guinevere Larsen
2026-01-09 12:36 ` Ciaran Woodward
2026-01-09 13:40 ` Guinevere Larsen
2026-01-09 14:16 ` Ciaran Woodward
2026-01-09 14:26 ` Guinevere Larsen
2026-01-09 16:53 ` Ciaran Woodward
2026-01-12 15:33 ` Andrew Burgess [this message]
2026-01-13 18:23 ` Guinevere Larsen
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=878qe2vo9z.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=ciaranwoodward@xmos.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@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