Re: [PATCH v2] gdb: make "start" breakpoint inferior-specific

[Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>]

On 11/11/22 20:03, Simon Marchi via Gdb-patches wrote:
>> I'm not sure if this is a better solution: it's more intrusive.
> Ah, that would be good too.  We wouldn't have to bake in the knowledge
> of which languages use which operator.  But I'm also a bit scared of
> other unintended consequences when looking up the main symbol, as I see
> the current_language is involved in some places.  To be safe, I'll just
> go with my naive patch.  Thanks for the suggestion.

FWIW, I've just stumbled onto language unknown, and realized that 
strictly speaking we've got a regression because we used to have:
...
$ gdb -q -batch a.out -ex "set language unknown" -ex start
Temporary breakpoint 1 at 0x40050b: file /home/vries/hello.c, line 6.

Temporary breakpoint 1, main () at /home/vries/hello.c:6
6         printf ("hello\n");
Warning: the current language does not match this frame.
$
...
but now we have:
...
$ gdb -q -batch a.out -ex "set language unknown" -ex start
expression parsing not implemented for language "Unknown"
$
...

I don't really care about this, I thought I just mention it.

Thanks,
- Tom