RE: [PATCH v2 2/2] gdb: add warning when no native target is available

Ciaran Woodward
2026-01-09T16:54:27Z

> 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