From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 00E60393A40D; Mon, 3 May 2021 12:46:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 00E60393A40D From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug threads/27812] New: [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: Mon, 03 May 2021 12:46:39 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: Mon, 03 May 2021 12:46:40 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27812 Bug ID: 27812 Summary: [m32] linux-nat.c:1765: internal-error: virtual void linux_nat_target::resume(ptid_t, int, gdb_signal): Assertion `signo =3D=3D GDB_SIGNAL_0' failed Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: threads Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- On the openSUSE tumbleweed gdb package (based on gdb 10.1) when testing on target board unix/-m32/-fno-PIE/-no-pie, I run into: ... FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: step thread 3 FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: first continue FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: second continue = (GDB internal error) FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: third continue (= the program is no longer running) ... In more detail: ... (gdb) PASS: gdb.threads/simultaneous-step-resume-breakpoint.exp: step threa= d 2 step^M sleep: Invalid argument^M simultaneous-step-resume-breakpoint: /home/abuild/rpmbuild/BUILD/gdb-10.1/gdb/testsuite/gdb.threads/simultaneous= -step-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 0xf7dcbb40 (LWP 24281)]^M 0xf7fd5159 in __kernel_vsyscall ()^M (gdb) FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: step threa= d 3 continue^M Continuing.^M sleep: Invalid argument^M simultaneous-step-resume-breakpoint: /home/abuild/rpmbuild/BUILD/gdb-10.1/gdb/testsuite/gdb.threads/simultaneous= -step-resume-breakpoint.c:48: func: Assertion `i =3D=3D 0' failed.^M ^M Thread 3 received signal SIGABRT, Aborted.^M [Switching to Thread 0xf75cab40 (LWP 24294)]^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 ../../gdb/linux-nat.c:1765: internal-error: virtual void linux_nat_target::resume(ptid_t, int, gdb_signal): Assertion `signo =3D=3D GDB_SIGNAL_0' failed.^M A problem internal to GDB has been detected,^M further debugging may prove unreliable.^M Quit this debugging session? (y or n) FAIL: gdb.threads/simultaneous-step-resume-breakpoint.exp: second continue (GDB internal error) ... --=20 You are receiving this mail because: You are on the CC list for the bug.=