[Bug breakpoints/12312] New: repeated watchpoints hits withbreakpoint always-inserted

["jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12312

           Summary: repeated watchpoints hits with breakpoint
                    always-inserted
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
        AssignedTo: unassigned@sourceware.org
        ReportedBy: jan.kratochvil@redhat.com
              Host: x86_64-fedora14-linux-gnu
            Target: x86_64-fedora14-linux-gnu


There was a fix:
[patch 1/4] Fix hw watchpoints #2: [x86*] repeated rwatch output
http://sourceware.org/ml/gdb-patches/2009-11/msg00350.html

which fixes it for breakpoint always-inserted off.  But for breakpoint
always-inserted on it still broken:

echo 'int a;f(){}main(){a=0;f();}'|gcc -g -x c -;gdb -q -nx -ex 'set breakpoint
always-inserted on' ./a.out -ex start -ex 'awatch a' -ex 'b f' -ex c -ex c
[...]
Continuing.
Hardware access (read/write) watchpoint 2: a
Value = 0
0x0000000000400488 in main () at <stdin>:1
1       in <stdin>
Continuing.
Hardware access (read/write) watchpoint 2: a
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ = bogus second hit
Value = 0
Breakpoint 3, f () at <stdin>:1
1       in <stdin>


In fact even in breakpoint always-inserted off the change is wrong as GDB may
stop without dealing with such event now, it may delay any event till the next
stop.
FYI bpstat evaluations vs. breakpoint hits
http://sourceware.org/ml/archer/2010-q4/msg00026.html
But I do not have a reproducer for it now.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.