public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "petr.sumbera at oracle dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30252] gdb-13.1/gdb/target.c:2641: internal-error: target_resume: Assertion `inferior_ptid != null_ptid' failed Date: Tue, 21 Mar 2023 09:08:23 +0000 [thread overview] Message-ID: <bug-30252-4717-ekzaPNN3H1@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30252-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30252 --- Comment #1 from Petr Šumbera <petr.sumbera at oracle dot com> --- The problematic commit added following two assertions: https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdb/target.c;h=0cebecfafc379534180a6563d246cdbc3488311e;hb=HEAD#l2648 2648 gdb_assert (inferior_ptid != null_ptid); 2649 gdb_assert (inferior_ptid.matches (scope_ptid)); When they are removed it seems to work as expected/before. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-21 9:08 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-20 16:00 [Bug gdb/30252] New: " petr.sumbera at oracle dot com 2023-03-20 16:01 ` [Bug gdb/30252] " petr.sumbera at oracle dot com 2023-03-21 9:08 ` petr.sumbera at oracle dot com [this message] 2023-03-21 14:55 ` [Bug tdep/30252] " tromey at sourceware dot org 2023-03-22 1:02 ` simark at simark dot ca 2023-03-22 8:06 ` petr.sumbera at oracle dot com 2023-03-23 16:13 ` pedro at palves dot net 2023-03-23 17:36 ` pedro at palves dot net 2023-03-24 8:06 ` petr.sumbera at oracle dot com 2023-06-12 20:16 ` marcel at telka dot sk 2023-07-06 14:10 ` cvs-commit at gcc dot gnu.org 2023-07-06 14:12 ` cvs-commit at gcc dot gnu.org 2023-07-06 14:15 ` pedro at palves dot net
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-30252-4717-ekzaPNN3H1@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).