diff options
| -rw-r--r-- | gdb/testsuite/ChangeLog | 4 | ||||
| -rw-r--r-- | gdb/testsuite/gdb.threads/execl.exp | 7 |
2 files changed, 11 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index f6b1a56..6fc24e1 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,5 +1,9 @@ 2020-03-12 Tom de Vries <tdevries@suse.de> + * gdb.threads/execl.exp: Delete breakpoint after hitting it. + +2020-03-12 Tom de Vries <tdevries@suse.de> + * gdb.fortran/module.exp: Use exp_continue during matching of output of "info variable -n". diff --git a/gdb/testsuite/gdb.threads/execl.exp b/gdb/testsuite/gdb.threads/execl.exp index 5f28fed..1649081 100644 --- a/gdb/testsuite/gdb.threads/execl.exp +++ b/gdb/testsuite/gdb.threads/execl.exp @@ -42,6 +42,13 @@ gdb_test "continue" ".*breakpoint here.*" "continue to exec" gdb_test "info threads" "1 *Thread.*2 *Thread.*3 *Thread.*" "info threads before exec" +# Work around PR25656, where the breakpoint above sets 2 breakpoint locations: +# - one on gdb.threads/execl.c:$linenumber, and +# - one in GLIBC's execl.c:$linenumber, in __GI_execl +# Delete the breakpoint to make sure we hit main upon continue, rather than +# __GI_execl. +gdb_test_no_output "delete 2" + # When continuing from this point we'll hit the breakpoint in main() # again, this time in the exec'd process. gdb_test "continue" ".*Breakpoint 1, main.*" \ |