public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28512] [aarch64] waitstatus.h:300: internal-error: gdb_signal target_waitstatus::sig() const: Assertion `m_kind == TARGET_WAITKIND_STOPPED || m_kind == TARGET_WAITKIND_SIGNALLED' failed. Date: Thu, 28 Oct 2021 09:06:02 +0000 [thread overview] Message-ID: <bug-28512-4717-3GylwkPIyz@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28512-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28512 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simark at simark dot ca --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- I wonder whether this is fixed by "[PATCH 3/3] gdb, gdbserver: make target_waitstatus safe" ( https://sourceware.org/pipermail/gdb-patches/2021-October/182502.html ). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-28 9:06 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-28 9:03 [Bug gdb/28512] New: " vries at gcc dot gnu.org 2021-10-28 9:06 ` vries at gcc dot gnu.org [this message] 2021-10-28 11:49 ` [Bug gdb/28512] " simark at simark dot ca 2021-10-28 12:25 ` vries at gcc dot gnu.org 2021-10-28 12:28 ` luis.machado at linaro dot org 2021-10-28 12:35 ` vries at gcc dot gnu.org 2021-10-28 12:40 ` luis.machado at linaro dot org 2021-10-28 12:49 ` [Bug gdb/28512] " vries at gcc dot gnu.org 2021-10-28 14:31 ` simon.marchi at polymtl dot ca 2021-10-28 16:30 ` simon.marchi at polymtl dot ca 2021-12-09 2:03 ` cvs-commit at gcc dot gnu.org 2021-12-09 2:04 ` simark at simark dot ca 2021-12-09 2:05 ` simark at simark dot ca
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-28512-4717-3GylwkPIyz@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).