diff options
| author | Tom de Vries <tdevries@suse.de> | 2025-04-23 19:10:22 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2025-04-23 19:10:22 +0200 |
| commit | 26011e4e104437220095003933df51633c8e966b (patch) | |
| tree | b8876233aa6bb6f7b1a2321576a7ffaf8e51dc06 /gdb/testsuite/boards/dwarf4-gdb-index.exp | |
| parent | 37f5e02ef5be1ba47e80df4af690df26ee1dac83 (diff) | |
| download | binutils-master.zip binutils-master.tar.gz binutils-master.tar.bz2 | |
With a gdb 16.2 based package, I ran into:
...
(gdb) PASS: gdb.base/bg-execution-repeat.exp: c 1&: input still accepted
interrupt
(gdb) PASS: gdb.base/bg-execution-repeat.exp: c 1&: interrupt
set var do_wait=0
(gdb) PASS: gdb.base/bg-execution-repeat.exp: c 1&: set var do_wait=0
continue&
Cannot execute this command while the selected thread is running.
(gdb)
Program received signal SIGINT, Interrupt.
PASS: gdb.base/bg-execution-repeat.exp: c 1&: continue&
0x00007ffff7cf1503 in clock_nanosleep@GLIBC_2.2.5 () from /lib64/libc.so.6
FAIL: gdb.base/bg-execution-repeat.exp: c 1&: breakpoint hit 2 (timeout)
...
Fix this by waiting for "Program received signal SIGINT, Interrupt" after
issuing the interrupt command.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/testsuite/boards/dwarf4-gdb-index.exp')
0 files changed, 0 insertions, 0 deletions