diff options
| author | Tom de Vries <tdevries@suse.de> | 2025-04-09 12:10:10 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2025-04-09 12:10:10 +0200 |
| commit | 92d4a12d9e924fc286c20e4199c270f270672d87 (patch) | |
| tree | 5b89ce600dac50e12d8533074f9c062160f2385f /gdb/testsuite/gdb.base/value-double-free.c | |
| parent | 1bafda2c4595f0f936a5845caf9667b70b198091 (diff) | |
| download | binutils-master.zip binutils-master.tar.gz binutils-master.tar.bz2 | |
[gdb/testsuite] Allow thread exited message in gdb.threads/infcall-from-bp-cond-simple.expHEADmaster
With a gdb 15.2 based package and test-case
gdb.threads/infcall-from-bp-cond-simple.exp, I ran into:
...
Thread 2 "infcall-from-bp" hit Breakpoint 3, function_with_breakpoint () at \
infcall-from-bp-cond-simple.c:51
51 return 1; /* Nested breakpoint. */
Error in testing condition for breakpoint 2:
The program being debugged stopped while in a function called from GDB.
Evaluation of the expression containing the function
(function_with_breakpoint) will be abandoned.
When the function is done executing, GDB will silently stop.
[Thread 0x7ffff73fe6c0 (LWP 951822) exited]
(gdb) FAIL: $exp: target_async=on: target_non_stop=on: \
run_bp_cond_hits_breakpoint: continue
...
The test fails because it doesn't expect the "[Thread ... exited]" message.
I have tried to reproduce this test failure, both using 15.2 and current
trunk, but haven't managed.
Regardless, I think the message is harmless, so allow it to occur, both in
run_bp_cond_segfaults and run_bp_cond_hits_breakpoint.
Tested on x86_64-linux.
PR testsuite/32785
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32785
Diffstat (limited to 'gdb/testsuite/gdb.base/value-double-free.c')
0 files changed, 0 insertions, 0 deletions