From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 3CD30382E52A; Tue, 15 Nov 2022 11:20:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3CD30382E52A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1668511219;
	bh=oBZl5FydDXjHN/m96uh19OvZZ2viTmkXKsJD57YD/aY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=NrHCxJW8M3fAp66GMonGOEtpv7gT0fbMg6Mshlx7Fj0gIIMjs5HMhlh3gr6b8X7XH
	 aUB+5KbqZfVaAYgPyrKAsTz7/jnWmpjlFANZIZrIiBalaATWv+rd/YlhVQ/lC6YF/U
	 l1SS2rM49CUae/HQf7Usn3uyJ+f5/p+apyd6mZEc=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28275] commit_resumed_state assertion failure when killing
 running inferior and running again
Date: Tue, 15 Nov 2022 11:20:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
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: <bug-28275-4717-ru3RHutOVL@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28275-4717@http.sourceware.org/bugzilla/>
References: <bug-28275-4717@http.sourceware.org/bugzilla/>
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
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D28275

--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #7)
> (In reply to Tom de Vries from comment #6)
> > (In reply to Simon Marchi from comment #5)
> > > Can you give specific test names?  I can try to build a GDB without e=
xpat
> > > and run those tests.
> >=20
> > I've deinstalled libexpat-devel and I'm doing a rerun.  Will let you kn=
own.
>=20
>=20
> In this particular run I get only 26 hits, all in gdb.server/ext-attach.e=
xp:
> ...
> $ egrep -i -a "^Running /|internal-error.*assertion" gdb.log \
>   | sed 's/^(gdb) //' \
>   | uniq -c \
>   | grep -i -B1 "internal-error.*assertion"
>       1 Running
> /suse/tdevries/gdb/src/gdb/testsuite/gdb.server/ext-attach.exp ...
>      26 /suse/tdevries/gdb/src/gdb/target.c:2590: internal-error:
> target_wait: Assertion `!proc_target->commit_resumed_state' failed.
> ...

Hmm, and we're running the test-case because aarch64 is not skipped in
skip_gdbserver_tests:
...
    # If GDB is lack of XML support, and targets, like arm, have=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20
    # multiple target descriptions, GDB doesn't know which target=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
    # description GDBserver uses, and may fail to parse 'g' packet=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20
    # after connection.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
    if { [gdb_skip_xml_test]
         && ([istarget "arm*-*-linux*"]
             || [istarget "mips*-*-linux*"]
             || [istarget "powerpc*-*-linux*"]
             || [istarget "s390*-*-linux*"]
             || [istarget "x86_64-*-linux*"]
             || [istarget "i\[34567\]86-*-linux*"]) } {
        return 1
    }
...

--=20
You are receiving this mail because:
You are on the CC list for the bug.=