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 gdb/28275] commit_resumed_state assertion failure when killing running inferior and running again
Date: Tue, 15 Nov 2022 11:20:18 +0000	[thread overview]
Message-ID: <bug-28275-4717-ru3RHutOVL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28275-4717@http.sourceware.org/bugzilla/>

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

--- 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 expat
> > > and run those tests.
> > 
> > I've deinstalled libexpat-devel and I'm doing a rerun.  Will let you known.
> 
> 
> In this particular run I get only 26 hits, all in gdb.server/ext-attach.exp:
> ...
> $ 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                
    # multiple target descriptions, GDB doesn't know which target               
    # description GDBserver uses, and may fail to parse 'g' packet              
    # after connection.                                                         
    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
    }
...

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

  parent reply	other threads:[~2022-11-15 11:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 14:35 [Bug gdb/28275] New: " simark at simark dot ca
2021-08-26 19:39 ` [Bug gdb/28275] " andrew.burgess at embecosm dot com
2021-10-29  9:22 ` nyanpasu64 at tuta dot io
2021-10-29 12:54 ` simark at simark dot ca
2022-11-14 15:02 ` vries at gcc dot gnu.org
2022-11-14 15:29 ` simark at simark dot ca
2022-11-14 16:32 ` vries at gcc dot gnu.org
2022-11-15  7:34 ` vries at gcc dot gnu.org
2022-11-15 11:20 ` vries at gcc dot gnu.org [this message]
2022-11-15 12:55 ` vries at gcc dot gnu.org
2022-11-16 15:36 ` aburgess at redhat dot com
2022-11-22 15:29 ` brobecker at gnat dot com
2022-11-28 13:03 ` cvs-commit at gcc dot gnu.org
2022-11-28 14:13 ` cvs-commit at gcc dot gnu.org
2022-11-28 14:14 ` simark at simark dot ca
2022-12-01 15:07 ` cvs-commit at gcc dot gnu.org
2022-12-01 15:07 ` cvs-commit at gcc dot gnu.org
2023-01-04  9:15 ` vries at gcc dot gnu.org
2023-01-04  9:57 ` brobecker at gnat dot com

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-28275-4717-ru3RHutOVL@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).