public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/27812] [m32] linux-nat.c:1765: internal-error: virtual void linux_nat_target::resume(ptid_t, int, gdb_signal): Assertion `signo == GDB_SIGNAL_0' failed
Date: Thu, 06 May 2021 15:26:19 +0000 [thread overview]
Message-ID: <bug-27812-4717-lb4MrIpnR0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27812-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27812
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #4 from Simon Marchi <simark at simark dot ca> ---
Am I crazy or... I don't see a
gdb.threads/simultaneous-step-resume-breakpoint.exp test.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-06 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 12:46 [Bug threads/27812] New: " vries at gcc dot gnu.org
2021-05-03 12:50 ` [Bug threads/27812] " vries at gcc dot gnu.org
2021-05-03 12:51 ` vries at gcc dot gnu.org
2021-05-06 15:18 ` vries at gcc dot gnu.org
2021-05-06 15:26 ` simark at simark dot ca [this message]
2021-05-06 15:29 ` vries at gcc dot gnu.org
2021-05-06 15:41 ` simark at simark dot ca
2021-05-07 17:48 ` vries at gcc dot gnu.org
2021-05-08 4:18 ` vries at gcc dot gnu.org
2021-05-09 7:36 ` vries at gcc dot gnu.org
2021-05-09 8:51 ` vries at gcc dot gnu.org
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-27812-4717-lb4MrIpnR0@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: link
Be 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).