[PATCH 0/2] Breakpoint conditions at locations with differing contexts

[Jonah Graham]

On Wed., Apr. 7, 2021, 17:24 Simon Marchi, <simon.marchi@polymtl.ca> wrote:

> On 2021-04-05 1:45 p.m., Jonah Graham wrote:> On Fri, 31 Jul 2020 at
> 11:42, Tankut Baris Aktemur via Gdb-patches <
> >
> 26^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="<MULTIPLE>",cond="invalid
> > condition
> >
> here",times="0",original-location="main"},{number="1.1",enabled="N*",addr="0x0000000000001160",func="main",file="../src/bug572589.c",fullname="/scratch/eclipse/src/cdt/runtime-CDT/bug572589/src/bug572589.c",line="20",thread-groups=["i1"]}
>
> Hi Jonah,
>
> Off-topic, but if you look at the MI output above, you'll note that it's
> not valid syntax.  A proper / strict MI parser should reject it.  This
> has been fixed in MI3:
>
>
> https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Development-and-Front-Ends.html#GDB_002fMI-Development-and-Front-Ends
>
> So you might want to consider upgrading to MI3 for GDB versions >= 9.1.
>

Thanks Simon for fixing that bug, there are some workarounds in the front
end for that. MI3 is on my to do list, I guess that is reason to raise it
higher up!

Jonah


> This is the commit that fixed it:
>
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b4be1b0648608a2578bbed39841c8ee411773edd
>
> Simon
>