From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BEF1E386FC05; Sun, 9 May 2021 07:36:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BEF1E386FC05 From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2021 07:36:10 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27812 --- Comment #9 from Tom de Vries --- 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 =3D=3D GDB_SIGNAL_0); + if (!((signo =3D=3D 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 threa= d 2 step^M sleep: Invalid argument^M simultaneous-step-resume-breakpoint: /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.threads/simultaneous-s= tep-resume-breakpoint.c:48: func: Assertion `i =3D=3D 0' failed.^M sleep: Invalid argument^M simultaneous-step-resume-breakpoint: /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.threads/simultaneous-s= tep-resume-breakpoint.c:48: func: Assertion `i =3D=3D 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 threa= d 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 cont= inue 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 cont= inue (the program is no longer running) ... --=20 You are receiving this mail because: You are on the CC list for the bug.=