public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "enedil at outlook 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, 01 Apr 2021 13:52:30 +0000 [thread overview] Message-ID: <bug-27682-4717-dfQARUkhoe@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27682-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27682 Michał Radwański <enedil at outlook dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Continue event in Python |Continue event in Python |delivered after thread dies |delivered after thread | |dies: internal-error: | |thread_info* | |inferior_thread(): | |Assertion `current_thread_ | |!= nullptr' failed. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-01 13:52 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 ` enedil at outlook dot com [this message] 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-09-16 1:11 ` parke.nexus at gmail dot com
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-dfQARUkhoe@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).