aboutsummaryrefslogtreecommitdiff
path: root/sim/m4
diff options
context:
space:
mode:
authorKevin Buettner <kevinb@redhat.com>2023-12-06 20:08:53 -0700
committerKevin Buettner <kevinb@redhat.com>2023-12-06 20:09:51 -0700
commit062e89021ece6132d226776ef6131e693ee11630 (patch)
tree1dd5c85ec64290c9538c9579234d3e30a3bdff26 /sim/m4
parentd86cb16645fbb8be6e92f8030e8bd885fe3ef44f (diff)
downloadgdb-062e89021ece6132d226776ef6131e693ee11630.zip
gdb-062e89021ece6132d226776ef6131e693ee11630.tar.gz
gdb-062e89021ece6132d226776ef6131e693ee11630.tar.bz2
Add more 'step' tests to gdb.base/watchpoint.exp
The test gdb.base/watchpoint.exp has a proc named 'test_stepping' which claims to "Test stepping and other mundane operations with watchpoints enabled". It sets a watchpoint on ival2, performs an inferior function call (which is not at all mundane), and uses 'next', 'until', and, finally, does a 'step'. However, that final 'step' command steps to (but not over/through) the line at which the assignment to ival2 takes place. At no time while performing these operations is a watchpoint hit. This commit adds a test to see what happens when stepping over/through the assignment to ival2. The watchpoint on ival2 should be triggered during this step. I've added another 'step' to make sure that the correct statement is reached after performing the watchpoint-hitting step. After running the 'test_stepping' proc, gdb.base/watchpoint.exp does a clean_restart before doing further tests, so nothing depends upon 'test_stepping' to stop at the particular statement at which it had been stopping. I've examined all tests which set watchpoints and step. I haven't been able to identify a(nother) test case which tests what happens when stepping over/through a statement which triggers a watchpoint. Therefore, adding these new 'step' tests is testing something which hasn't being tested elsewhere. Reviewed-By: John Baldwin <jhb@FreeBSD.org>
Diffstat (limited to 'sim/m4')
0 files changed, 0 insertions, 0 deletions