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 server/29253] New: [gdb, server] FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=threads: continue to main (timeout) Date: Thu, 16 Jun 2022 08:09:27 +0000 [thread overview] Message-ID: <bug-29253-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29253 Bug ID: 29253 Summary: [gdb, server] FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=threads: continue to main (timeout) Product: gdb Version: 12.1 Status: NEW Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With gdb 12.1, on OBS for openSUSE Tumbleweed with target boards unix/-m32 and unix/-m32/-fno-PIE/-no-pie: ... (gdb) c^M Continuing.^M warning: Could not load shared library symbols for linux-gate.so.1.^M Do you need "set solib-search-path" or "set sysroot"?^M FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=threads: continue to main (timeout) ... The interesting bit is that this occurred in two runs, so it's not a fluke. Unfortunately, I could not reproduce outside of OBS, even with building from the package sources. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-06-16 8:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-16 8:09 vries at gcc dot gnu.org [this message] 2022-06-16 8:11 ` [Bug server/29253] " vries at gcc dot gnu.org 2022-06-16 14:13 ` 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-29253-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).