[Bug mi/28077] New: -exec-interrupt in non-stop mode causes internal-error / assertion in target_stop

["jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 28077
           Summary: -exec-interrupt in non-stop mode causes internal-error
                    / assertion in target_stop
           Product: gdb
           Version: 11.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: jonah at kichwacoders dot com
  Target Milestone: ---

This is a regression in GDB 11 pre-release and current HEAD that worked in GDB
10.

For a simple program like this loop.c.

volatile int i;
int main() {
  while (1) {
    i += 2;
    i *= 2;
  }
}

gcc -g -o loop loop.c

causes an internal error like this when doing -exec-interrupt in MI mode, it
does not fail in CLI mode.

target.c:3768: internal-error: void target_stop(ptid_t): Assertion
`!proc_target->commit_resumed_state' failed.

MI commands to reproduce:

$ gdb --interpreter=mi3 # or mi2
-gdb-set non-stop on
-gdb-set mi-async on
-file-exec-and-symbols --thread-group i1  loop
-exec-run
-exec-interrupt --thread-group i1

This was done on Ubuntu 20.04 on x86_64 hardware:
$ lsb_release 
LSB Version:    core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
$ uname -a
Linux ditto 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
$ gcc --version
gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0

I am running a git bisect now and will report back if that provides something
useful.

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