[Bug breakpoints/30335] Watchpoints aren't triggered when calling program functions

["joe at lothan dot net" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30335

--- Comment #1 from Joe Lothan <joe at lothan dot net> ---
Forgot to mention that breakpoints do trigger when calling program functions,
it's just watchpoints that do not. And interestingly enough, when a breakpoint
is hit, it allows the watchpoint to be hit later in the program function
execution.

Using the same example: 
$ gdb -q ./test
Reading symbols from ./test...
(gdb) break main
Breakpoint 1 at 0x118b: file test.c, line 11.
(gdb) run
Starting program: /home/joe/test
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, main () at test.c:11
11          for (int i = 0; i < 5; i++)
(gdb) watch towatch
Hardware watchpoint 2: towatch
(gdb) break change_var
Breakpoint 3 at 0x555555555151: file test.c, line 6.
(gdb) call change_var()

Breakpoint 3, change_var () at test.c:6
6           towatch ++;
The program being debugged stopped while in a function called from GDB.
Evaluation of the expression containing the function
(change_var) will be abandoned.
When the function is done executing, GDB will silently stop.
(gdb) finish
Run till exit from #0  change_var () at test.c:6

Hardware watchpoint 2: towatch

Old value = 0
New value = 1
change_var () at test.c:7
7           printf("new towatch: %d\n", towatch);
(gdb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.