aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python/py-cmd-exception.py
diff options
context:
space:
mode:
authorSébastien Darche <sdarche@efficios.com>2025-09-26 16:37:54 -0400
committerSébastien Darche <sdarche@efficios.com>2025-10-08 15:43:33 -0400
commitd3758513a81c81d6e62b135bff43ecca6608a65d (patch)
tree0b33982c1a4d17128d4892c6f3aebe2751810f18 /gdb/testsuite/gdb.python/py-cmd-exception.py
parent30136f5aeffa98a8346ff364d5ad59f667026843 (diff)
downloadbinutils-d3758513a81c81d6e62b135bff43ecca6608a65d.zip
binutils-d3758513a81c81d6e62b135bff43ecca6608a65d.tar.gz
binutils-d3758513a81c81d6e62b135bff43ecca6608a65d.tar.bz2
[gdb/testsuite] fix gdb.server/server-kill.exp
A test case in gdb.server/server-kill.exp attempts to query the server status after the server it is connected to has been killed. The connection is reset as expected, but the regex on the error message seems to be out-of-date. The test expects: Remote communication error. Target disconnected: Connection reset by peer. But a modern build of gdb yields : Remote communication error. Target disconnected: error while reading: Connection reset by peer. I presume this is due to change 0da23004a064 ("Change serial_readchar to throw") which added exceptions to the control flow handling instead of relying on perror(). The exception error string inserts "error while reading" to the perror message. The test appeared to fail intermittently, sometimes matching the first part of the regex ("Remote connection closed"). It now passes consistently. Change-Id: I3bf364b5d4b56de67f9ca30e9d636d3bb1be4119 Approved-by: Kevin Buettner <kevinb@redhat.com>
Diffstat (limited to 'gdb/testsuite/gdb.python/py-cmd-exception.py')
0 files changed, 0 insertions, 0 deletions