public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/31001] New: [gdb] UNRESOLVED: gdb.threads/async.exp: thread 1: current thread is 1
@ 2023-10-26 13:11 vries at gcc dot gnu.org
  2023-10-26 13:12 ` [Bug gdb/31001] " vries at gcc dot gnu.org
  0 siblings, 1 reply; 2+ messages in thread
From: vries at gcc dot gnu.org @ 2023-10-26 13:11 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=31001

            Bug ID: 31001
           Summary: [gdb] UNRESOLVED: gdb.threads/async.exp: thread 1:
                    current thread is 1
           Product: gdb
           Version: 13.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With a gdb 13.2 based package on SLE-11 x86_64, I run into:
...
(gdb) PASS: gdb.threads/async.exp: thread 1: switch to thread 1
continue&^M
Continuing.^M
(gdb) PASS: gdb.threads/async.exp: thread 1: continue&
thread^M
[Current thread is 1 (Thread 0x155555546700 (LWP 24676))]^M
(gdb) thread^M
[Current thread is 1 (Thread 0x155555546700 (LWP 24676))]^M
(gdb) thread^M
[Current thread is 1 (Thread 0x155555546700 (LWP 24676))]^M
(gdb) thread^M
[Current thread is 1 (Thread 0x155555546700 (LWP 24676))]^M
(gdb) thread^M
ERROR: GDB process no longer exists
GDB process exited with wait status 24520 exp7 0 0
UNRESOLVED: gdb.threads/async.exp: thread 1: current thread is 1
...

I haven't been able to reproduce outside of Open Build Service yet.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread
* [Bug gdb/31001] [gdb] UNRESOLVED: gdb.threads/async.exp: thread 1: current thread is 1
  2023-10-26 13:11 [Bug gdb/31001] New: [gdb] UNRESOLVED: gdb.threads/async.exp: thread 1: current thread is 1 vries at gcc dot gnu.org
@ 2023-10-26 13:12 ` vries at gcc dot gnu.org
  0 siblings, 0 replies; 2+ messages in thread
From: vries at gcc dot gnu.org @ 2023-10-26 13:12 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=31001

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
I did manage to reproduce roughly the same output by doing:
...
$ kill -SIGTERM $(pidof gdb)
...
while the test is running:
...
(gdb) PASS: gdb.threads/async.exp: thread 1: continue&
thread^M
[Current thread is 1 (Thread 0x7ffff7c3b100 (LWP 18981))]^M
(gdb) thread^M
[Current thread is 1 (Thread 0x7ffff7c3b100 (LWP 18981))]^M
(gdb) thread^M
[Current thread is 1 (Thread 0x7ffff7c3b100 (LWP 18981))]^M
(gdb) thread^M
[Current thread is 1 (Thread 0x7ffff7c3b100 (LWP 18981))]^M
(gdb) thread^M
ERROR: GDB process no longer exists
GDB process exited with wait status 18963 exp9 0 0
UNRESOLVED: gdb.threads/async.exp: thread 1: current thread is 1
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-10-26 13:12 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-26 13:11 [Bug gdb/31001] New: [gdb] UNRESOLVED: gdb.threads/async.exp: thread 1: current thread is 1 vries at gcc dot gnu.org
2023-10-26 13:12 ` [Bug gdb/31001] " vries at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).