diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2021-11-24 14:22:43 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2021-11-24 14:34:36 -0500 |
| commit | e19f8248297bb9864ff14368cc89d2446572837a (patch) | |
| tree | 10f5e5dcefe2c864177aab06bab9f90294f0e3d8 /gdb | |
| parent | d8ed269e5c875845fcd0f1a25457eafe3f485249 (diff) | |
| download | gdb-e19f8248297bb9864ff14368cc89d2446572837a.zip gdb-e19f8248297bb9864ff14368cc89d2446572837a.tar.gz gdb-e19f8248297bb9864ff14368cc89d2446572837a.tar.bz2 | |
Revert (part of) "gdb fix for catch-syscall.exp"
This reverts (par of) commit ab198279120fe7937c0970a8bb881922726678f9.
This commit changed what the test expects when catching the execve
syscall based on the behavior seen on a Linux PowerPC machine. That is,
we get an "entry" event, but no "return" event. This is not what we get
on Linux with other architectures, though, and it seems like a
PowerPC-specific bug.
Revert the part of the patch related to this, but not the other hunk.
Change-Id: I4248776e4299f10999487be96d4acd1b33639996
Diffstat (limited to 'gdb')
| -rw-r--r-- | gdb/testsuite/gdb.base/catch-syscall.exp | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/gdb/testsuite/gdb.base/catch-syscall.exp b/gdb/testsuite/gdb.base/catch-syscall.exp index 016d0a6..cdd5e2a 100644 --- a/gdb/testsuite/gdb.base/catch-syscall.exp +++ b/gdb/testsuite/gdb.base/catch-syscall.exp @@ -348,9 +348,7 @@ proc test_catch_syscall_execve {} { # Check for entry/return across the execve, making sure that the # syscall_state isn't lost when turning into a new process. insert_catch_syscall_with_arg "execve" - - # Check that the execve is called. - check_call_to_syscall "execve" + check_continue "execve" # Continue to main so extended-remote can read files as needed. # (Otherwise that "Reading" output confuses gdb_continue_to_end.) |