public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "parke.nexus at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/27682] Continue event in Python delivered after thread dies: internal-error: thread_info* inferior_thread(): Assertion `current_thread_ != nullptr' failed. Date: Thu, 16 Sep 2021 01:11:56 +0000 [thread overview] Message-ID: <bug-27682-4717-nbGPenoXSi@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27682-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27682 Parke <parke.nexus at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |parke.nexus at gmail dot com --- Comment #1 from Parke <parke.nexus at gmail dot com> --- I encounter a similar bug. Easy to reproduce. On Arch Linux: $ gdb --version GNU gdb (GDB) 10.2 [snip] $ gdb -q -ex run /bin/true Reading symbols from /bin/true... (No debugging symbols found in /bin/true) Starting program: /usr/bin/true [Inferior 1 (process 339) exited normally] ../../gdb/thread.c:95: internal-error: thread_info* inferior_thread(): Assertion `current_thread_ != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. Aborted (core dumped) $ cat ~/.gdbinit define hook-quit set confirm off end python def exit_handler ( event ): if hasattr ( event, 'exit_code' ) and event .exit_code == 0: gdb .execute ( "quit" ) gdb .events .exited .connect ( exit_handler ) end ---- I encounter a similar bug on Ubuntu 20.04. $ gdb --version GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2 [snip] $ gdb -q -ex run /bin/true Reading symbols from /bin/true... (No debugging symbols found in /bin/true) Starting program: /usr/bin/true [Inferior 1 (process 4134946) exited normally] /build/gdb-OxeNvS/gdb-9.2/gdb/inferior.c:283: internal-error: inferior* find_inferior_pid(int): Assertion `pid != 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. This is a bug, please report it. For instructions, see: <http://www.gnu.org/software/gdb/bugs/>. Aborted (core dumped) Possibly related: https://sourceware.org/bugzilla/show_bug.cgi?id=26761 -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-09-16 1:11 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 13:51 [Bug python/27682] New: Continue event in Python delivered after thread dies enedil at outlook dot com 2021-04-01 13:52 ` [Bug python/27682] Continue event in Python delivered after thread dies: internal-error: thread_info* inferior_thread(): Assertion `current_thread_ != nullptr' failed enedil at outlook dot com 2021-04-01 13:52 ` enedil at outlook dot com 2021-09-16 1:11 ` parke.nexus at gmail dot com [this message]
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-27682-4717-nbGPenoXSi@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).