Multiple locations and breakpoints confusion.

Keith Seitz
Wed May 2 16:42:00 GMT 2018

On 05/02/2018 09:27 AM, Pedro Alves wrote:
>  (gdb) disable 1.1-2
>  (gdb) disable 1
>  (gdb) enable 1.1
>  (gdb) info breakpoints 
>  Num     Type           Disp Enb Address            What
>  1       breakpoint     keep n   <MULTIPLE>         
>  1.1                         y     0x00000000004004b3 in multiple_test::foo(int) at multiple.cpp:10
>  1.2                         n     0x00000000004004c3 in multiple_test::foo(double) at multiple.cpp:15
> Here, it seems very desirable to me to be able to tell that
> location 1.1 is going to be enabled if I decide to enable breakpoint 1.

While I don't find this confusing at all, I can certainly understand how a user might get a little confused.

Nonetheless, if we did want to mitigate the situation, we could add a UI-related tweak, such as adding a new column (yuck) or some sort of "footnote" explaining that the sub-location is currently disabled because the parent is disabled.

That would be a pretty simple change to the code base (but probably would have rather severe repercussions on the test suite to deal with).

Just my 10E-30 cents,

More information about the Gdb mailing list