Re: [PATCH] Remove same-pc breakpoint notification for internal BPs

[Pedro Alves <pedro at codesourcery dot com>]

On Thursday 21 April 2011 09:11:29, Kevin Pouget wrote:
> +               && b->number >= 0);

Can you make those b->number > 0?   `0' is used for
momentary breakpoints, which aren't user visible either.

(as principle, please re-paste the changelog when posting
an updated patch, so we don't have go fish which patch
goes with which changelog.  It's practicaly 0 work to re-paste
it, but it's not 0 work to look for it.)

In all-stop/sync when the user has the prompt,
no momentary breakpoint will be inserted (pending bugs), but
in non-stop, it can happen:

(gdb) next& (over a function call that never returns)
...
(gdb) maint info breakpoints 
Num     Type           Disp Enb Address            What
-1      shlib events   keep y   0x00007ffff7deba30 <_dl_debug_state> inf 1
        breakpoint already hit 2 times
...
0       step resume    keep y   0x0000000000400728 <main+164> inf 1 thread 1
        stop only in thread 1
(gdb) b *0x0000000000400728
Note: breakpoint 0 (thread 1) also set at pc 0x400728.
Breakpoint 2 at 0x400728: file threads.c, line 51.
(gdb) 

-- 
Pedro Alves