From: Ciaran Woodward <ciaranwoodward@xmos.com>
To: Guinevere Larsen <guinevere@redhat.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: Fri, 9 Jan 2026 16:53:52 +0000 [thread overview]
Message-ID: <AS8PR09MB5303E84C2A266D39B83CFD12B982A@AS8PR09MB5303.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <c9509cab-8de1-4870-b3f6-0ea106b88d6c@redhat.com>
> I think making it configure-time would essentially render this change
> useless
>
> I can't imagine anyone distributing GDB without native support where the
> distributor doesn't do it on purpose, so from their PoV it makes sense
> to disable the warning. However, a user in a Mac using M-series CPUs
> might not recognize or understand what they're reading, so this warning
> would be important but disabled for them.
To me this sounds like there will be many people who would get frustrated
to have the extra text then - if they are going to look for ways to disable
it.
My other experience is that new users don't necessarily read the intro blurb
that much.
> What I'm thinking is making -q suppress this warning, would that be
> enough for you?
If you do end up merging this change, I think that would be required, yes.
Although personally I still don't think this will be a helpful message
for many of the people that will see it.
What about moving the warning to the place that the user makes the error?
i.e. when they try to attach to/start a native program. it provides some of
this information.
That would be useful to everyone, and users are also more motivated to read
just after something has failed to work. Right now I get "Don't know how to
run. try help target", which is not as helpful as your new text imo.
Cheers,
Ciaran
next prev parent reply other threads:[~2026-01-09 16:54 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 [this message]
2026-01-12 15:33 ` Andrew Burgess
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=AS8PR09MB5303E84C2A266D39B83CFD12B982A@AS8PR09MB5303.eurprd09.prod.outlook.com \
--to=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