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 record/28086] New: inferior.c:303: internal-error: inferior* find_inferior _pid(process_stratum_target*, int): Assertion `pid != 0' failed. Date: Wed, 14 Jul 2021 07:12:28 +0000 [thread overview] Message-ID: <bug-28086-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28086 Bug ID: 28086 Summary: inferior.c:303: internal-error: inferior* find_inferior _pid(process_stratum_target*, int): Assertion `pid != 0' failed. Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- When running test-case gdb.btrace/enable-new-thread.exp on openSUSE tumbleweed, I run into: ... FAIL: gdb.btrace/enable-new-thread.exp: continue to breakpoint: cont to bp.1 (GDB internal error) ... In more detail: ... (gdb) record btrace^M (gdb) PASS: gdb.btrace/enable-new-thread.exp: record btrace break 24^M Breakpoint 2 at 0x40113e: file /data/gdb_versions/devel/src/gdb/testsuite/gdb.btrace/enable-new-thread.c, line 24.^M (gdb) continue^M Continuing.^M /data/gdb_versions/devel/src/gdb/inferior.c:303: internal-error: inferior* find_inferior_pid(process_stratum_target*, int): Assertion `pid != 0' failed.^M A problem internal to GDB has been detected,^M further debugging may prove unreliable.^M ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-07-14 7:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-14 7:12 vries at gcc dot gnu.org [this message] 2021-07-14 7:12 ` [Bug record/28086] " vries at gcc dot gnu.org 2021-07-14 7:14 ` vries at gcc dot gnu.org 2021-07-14 7:19 ` vries at gcc dot gnu.org 2021-07-14 9:33 ` vries at gcc dot gnu.org 2021-07-14 14:41 ` simark at simark dot ca 2021-07-14 15:13 ` vries at gcc dot gnu.org 2021-07-14 15:14 ` simark at simark dot ca 2021-07-14 15:30 ` simark at simark dot ca 2021-07-14 15:34 ` vries at gcc dot gnu.org 2021-07-19 13:45 ` cvs-commit at gcc dot gnu.org 2021-07-19 13:45 ` simark at simark dot ca 2021-10-12 9:41 ` 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-28086-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).