public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "brobecker at gnat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30240] (linux/aarch) thread.c:86: internal-error: inferior_thread: Assertion `current_thread_ != nullptr' failed. Date: Mon, 08 May 2023 01:12:53 +0000 [thread overview] Message-ID: <bug-30240-4717-f5Iy51Jc4h@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30240-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30240 Joel Brobecker <brobecker at gnat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |13.2 CC| |brobecker at gnat dot com --- Comment #9 from Joel Brobecker <brobecker at gnat dot com> --- Setting the target milestone to 13.2 as a way to record that this fix was included in the upcoming GDB 13.2 release. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-05-08 1:12 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-17 15:49 [Bug gdb/30240] New: " dmitry.neverov at jetbrains dot com 2023-03-17 17:18 ` [Bug gdb/30240] " simark at simark dot ca 2023-03-17 17:34 ` luis.machado at arm dot com 2023-03-17 17:36 ` luis.machado at arm dot com 2023-03-20 8:28 ` dmitry.neverov at jetbrains dot com 2023-03-23 10:45 ` luis.machado at arm dot com 2023-03-27 5:31 ` luis.machado at arm dot com 2023-03-31 8:33 ` dmitry.neverov at jetbrains dot com 2023-04-03 8:21 ` luis.machado at arm dot com 2023-05-08 1:12 ` brobecker at gnat 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-30240-4717-f5Iy51Jc4h@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).