espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-10-16 20:32:21 +08:00
Code Issues Packages Projects Releases Wiki Activity

* gdb.base/recurse.exp: When checking leaving the watchpoint

Browse Source 
scope, recognize when gdb is in function's epilogue and pass.
This commit is contained in:
Corinna Vinschen
2001-09-19 08:21:17 +00:00
parent 44addf7f7b
commit f3bcedc1a9
2 changed files with 28 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,8 @@
2001-09-19 Corinna Vinschen <vinschen@redhat.com>
* gdb.base/recurse.exp: When checking leaving the watchpoint
scope, recognize when gdb is in function's epilogue and pass.
2001-09-18 Keith Seitz <keiths@redhat.com> 2001-09-18 Keith Seitz <keiths@redhat.com>
* lib/insight-support.exp (_gdbtk_export_target_info): Add * lib/insight-support.exp (_gdbtk_export_target_info): Add

25
gdb/testsuite/gdb.base/recurse.exp
View File

@ -123,9 +123,30 @@ proc recurse_tests {} {
gdb_suppress_tests gdb_suppress_tests
} }
# Continue again. We should have a watchpoint go out of scope now # Continue again. We should have a watchpoint go out of scope now.
#
# The former version expected the test to return to main().
# Now it expects the test to return to main or to stop in the
# function's epilogue.
#
# The problem is that gdb needs to (but doesn't) understand
# function epilogues in the same way as for prologues.
#
# If there is no hardware watchpoint (such as a x86 debug register),
# then watchpoints are done "the hard way" by single-stepping the
# target until the value of the watched variable changes. If you
# are single-stepping, you will eventually step into an epilogue.
# When you do that, the "top" stack frame may become partially
# deconstructed (as when you pop the frame pointer, for instance),
# and from that point on, GDB can no longer make sense of the stack.
#
# A test which stops in the epilogue is trying to determine when GDB
# leaves the stack frame in which the watchpoint was created. It does
# this basically by watching for the frame pointer to change. When
# the frame pointer changes, the test expects to be back in main, but
# instead it is still in the epilogue of the callee.
if [gdb_test "continue" \ if [gdb_test "continue" \
"Continuing.*\[Ww\]atchpoint.*deleted.*main \\(\\) .*" \ "Continuing.*\[Ww\]atchpoint.*deleted.*\(main \\(\\) \|21.*\}\).*" \
"first instance watchpoint deleted when leaving scope"] then { "first instance watchpoint deleted when leaving scope"] then {
gdb_suppress_tests; gdb_suppress_tests;
} }