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] New: gdb-13.1/gdb/target.c:2641: internal-error: target_resume: Assertion `inferior_ptid != null_ptid' failed Date: Mon, 20 Mar 2023 16:00:19 +0000 [thread overview] Message-ID: <bug-30252-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30252 Bug ID: 30252 Summary: gdb-13.1/gdb/target.c:2641: internal-error: target_resume: Assertion `inferior_ptid != null_ptid' failed Product: gdb Version: 13.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: petr.sumbera at oracle dot com Target Milestone: --- I see following regression/internal-error when using gdb (13.1) on Solaris x86: (gdb) run -P Starting program: /usr/bin/firefox -P [Thread debugging using libthread_db enabled] warning: could not convert 'mutex_t' from the host encoding (ISO-8859-1) to UTF-32. This normally should not happen, please file a bug report. [New Thread 1 (LWP 1)] /builds/psumbera/userland-gdb-13/components/gdb/gdb-13.1/gdb/target.c:2641: internal-error: target_resume: Assertion `inferior_ptid != null_ptid' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. ----- Backtrace ----- 0x9b6213 ??? 0xd3e52c ??? 0xd3e778 ??? 0xe798bc ??? 0xcee510 ??? 0xbdefca ??? 0xc7273b ??? 0xcf1443 ??? 0xb3b9c4 ??? 0xb4d008 ??? 0x979b2f ??? 0xe7a684 ??? 0xb777f1 ??? 0xb791e4 ??? 0x922da6 ??? 0x922c12 ??? --------------------- /builds/psumbera/userland-gdb-13/components/gdb/gdb-13.1/gdb/target.c:2641: internal-error: target_resume: Assertion `inferior_ptid != null_ptid' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. -- I used git bisect and it says: d51926f06a7f4854bebdd71dcb0a78dbaa2f4168 is the first bad commit commit d51926f06a7f4854bebdd71dcb0a78dbaa2f4168 Author: Pedro Alves <pedro@palves.net> Date: Thu Apr 21 14:20:36 2022 +0100 Slightly tweak and clarify target_resume's interface -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-03-20 16:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-20 16:00 petr.sumbera at oracle dot com [this message] 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 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@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).