[Bug testsuite/34425] New: [gdb/testsuite] FAIL: gdb.threads/leader-exit.exp: single thread has been left
"vries at gcc dot gnu.org via Gdb-prs" <[email protected]>
| Newsgroups | gmane.comp.gdb.bugs.discuss |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://sourceware.org/bugzilla/show_bug.cgi?id=34425
Bug ID: 34425
Summary: [gdb/testsuite] FAIL: gdb.threads/leader-exit.exp:
single thread has been left
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Created attachment 16859
--> https://sourceware.org/bugzilla/attachment.cgi?id=16859&action=edit
gdb.log
On aarch64-linux, with taskset -c 0, I get:
...
(gdb) continue^M
Continuing.^M
[New Thread 0xfffff7d1f160 (LWP 62010) (id 2)]^M
[Switching to thread 2 (Thread 0xfffff7d1f160 (LWP 62010))]^M
^M
Thread 2 "leader-exit" hit Breakpoint 2, start (arg=0x0) at leader-exit.c:32^M
32 sleep (10); /* break-here */^M
(gdb) PASS: gdb.threads/leader-exit.exp: continue to breakpoint: break-here
info threads^M
Id Target Id Frame ^M
1 Thread 0xfffff7fe8020 (LWP 62008) "leader-exit" (Exiting)
0x0000fffff7d46fa0 \
in __libc_start_call_main () from /lib64/libc.so.6^M
* 2 Thread 0xfffff7d1f160 (LWP 62010) "leader-exit" start
(arg=0x0) at \
leader-exit.c:32^M
(gdb) FAIL: gdb.threads/leader-exit.exp: single thread has been left
...
In a passing version, we have a "Thread exited" message after the continue:
...
(gdb) continue^M
Continuing.^M
[New Thread 0xfffff7cef160 (LWP 1866680) (id 2)]^M
[Thread 0xfffff7ff0020 (LWP 1866678) (id 1) exited]^M
[Switching to thread 2 (Thread 0xfffff7cef160 (LWP 1866680))]^M
^M
Thread 2 "leader-exit" hit Breakpoint 2, start (arg=0x0) at leader-exit.c:32^M
32 sleep (10); /* break-here */^M
(gdb) PASS: gdb.threads/leader-exit.exp: continue to breakpoint: break-here
...
But here, that's missing.
--
You are receiving this mail because:
You are on the CC list for the bug.