public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31001] New: [gdb] UNRESOLVED: gdb.threads/async.exp: thread 1: current thread is 1 Date: Thu, 26 Oct 2023 13:11:48 +0000 [thread overview] Message-ID: <bug-31001-4717@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2023-10-26 13:11 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-26 13:11 vries at gcc dot gnu.org [this message] 2023-10-26 13:12 ` [Bug gdb/31001] " vries at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31001-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).