OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* gdb.base/foll-fork.exp: Make regexps to match catchpoint hits more 

strict, but do not check for any particular function name within libc.
This commit is contained in:
Ulrich Weigand 2010-10-19 21:28:33 +00:00
parent 79afc5ef5d
commit 2c04da0de0
2 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,8 @@
2010-10-19 Ulrich Weigand <uweigand@de.ibm.com>
* gdb.base/foll-fork.exp: Make regexps to match catchpoint hits more
strict, but do not check for any particular function name within libc.
2010-10-19 Sami Wagiaalla <swagiaal@redhat.com>
* gdb.cp/smartp.exp: New test.

11
gdb/testsuite/gdb.base/foll-fork.exp
View File

@ -122,7 +122,7 @@ proc catch_fork_child_follow {} {
set bp_after_fork [gdb_get_line_number "set breakpoint here"]
gdb_test "catch fork" "Catchpoint .*(fork).*" \
gdb_test "catch fork" "Catchpoint \[0-9\]* \\(fork\\)" \
"explicit child follow, set catch fork"
# Verify that the catchpoint is mentioned in an "info breakpoints",
@ -136,7 +136,7 @@ proc catch_fork_child_follow {} {
}
gdb_test "continue" \
"Catchpoint.*(forked process.*),.*in .*(fork|__kernel_v?syscall).*" \
"Catchpoint \[0-9\]* \\(forked process \[0-9\]*\\),.*" \
"explicit child follow, catch fork"
# Verify that the catchpoint is mentioned in an "info breakpoints",
@ -184,7 +184,7 @@ proc catch_fork_unpatch_child {} {
"unpatch child, set catch fork"
gdb_test "continue" \
"Catchpoint.*\\(forked process.*\\).*,.*in .*(fork|__kernel_v?syscall).*" \
"Catchpoint \[0-9\]* \\(forked process \[0-9\]*\\),.*" \
"unpatch child, catch fork"
# Delete all breakpoints and catchpoints.
@ -225,14 +225,15 @@ proc tcatch_fork_parent_follow {} {
set bp_after_fork [gdb_get_line_number "set breakpoint here"]
gdb_test "catch fork" "Catchpoint .*(fork).*" \
gdb_test "catch fork" "Catchpoint \[0-9\]* \\(fork\\)" \
"explicit parent follow, set tcatch fork"
# ??rehrauer: I don't yet know how to get the id of the tcatch
# via this script, so that I can add a -do list to it. For now,
# do the follow stuff after the catch happens.
gdb_test "continue" "in .*(fork|__kernel_v?syscall).*" \
gdb_test "continue" \
"Catchpoint \[0-9\]* \\(forked process \[0-9\]*\\),.*" \
"explicit parent follow, tcatch fork"
gdb_test_no_output "set follow-fork parent"