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 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: Sun, 09 May 2021 07:36:10 +0000 [thread overview] Message-ID: <bug-27812-4717-7tI87E1jfs@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27812-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27812 --- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> --- Using this patch (so, disabling the assert, and printing a message that it would have triggered otherwise): ... diff --git a/gdb/linux-nat.c b/gdb/linux-nat.c index c45e335a762..f0104f130cc 100644 --- a/gdb/linux-nat.c +++ b/gdb/linux-nat.c @@ -1712,7 +1712,8 @@ linux_nat_target::resume (ptid_t ptid, int step, enum gdb_signal signo) { /* FIXME: What should we do if we are supposed to continue this thread with a signal? */ - gdb_assert (signo == GDB_SIGNAL_0); + if (!((signo == GDB_SIGNAL_0))) + fprintf (stderr, "ASSERT TRIGGERED\n"); linux_nat_debug_printf ("Short circuiting for status 0x%x", lp->status); ... I get: ... (gdb) PASS: gdb.threads/simultaneous-step-resume-breakpoint.exp: step thread 2 step^M sleep: Invalid argument^M simultaneous-step-resume-breakpoint: /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.threads/simultaneous-step-resume-breakpoint.c:48: func: Assertion `i == 0' failed.^M sleep: Invalid argument^M simultaneous-step-resume-breakpoint: /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.threads/simultaneous-step-resume-breakpoint.c:48: func: Assertion `i == 0' failed.^M ^M Thread 2 "simultaneous-st" received signal SIGABRT, Aborted.^M [Switching to Thread 0xf7cb4b40 (LWP 18067)]^M 0xf7fd5159 in __kernel_vsyscall ()^M (gdb) FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: step thread 3 continue^M Continuing.^M ^M Thread 3 received signal SIGABRT, Aborted.^M [Switching to Thread 0xf74b3b40 (LWP 18068)]^M Cannot remove breakpoints because program is no longer writable.^M Further execution is probably impossible.^M 0xf7fd5159 in __kernel_vsyscall ()^M (gdb) FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: first continue continue^M Continuing.^M ASSERT TRIGGERED^M ^M Program terminated with signal SIGABRT, Aborted.^M The program no longer exists.^M (gdb) FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: second continue continue^M The program is not being run.^M (gdb) FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: third continue (the program is no longer running) ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-09 7:36 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 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 [this message] 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-7tI87E1jfs@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).