[Bug mi/18622] New: Erroneous "running" event while in suspended state messing up Eclipse DSF

[Bug mi/18622] New: Erroneous "running" event while in suspended state messing up Eclipse DSF

[jens.elmenthaler at advantest dot com]

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

            Bug ID: 18622
           Summary: Erroneous "running" event while in suspended state
                    messing up Eclipse DSF
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: jens.elmenthaler at advantest dot com
  Target Milestone: ---

Created attachment 8409
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8409&action=edit
Patch to suppress event for all-stop mode

I'm debugging a multi-threaded software written in C++ using Eclipse DSF in
all-stop mode. The gdb version is "GNU gdb (GDB) Red Hat Enterprise Linux
7.6.1-51.1.el7".

>From time to time threads are spawned or exited and if gdb detects this while
being suspended, an event "*running,thread-id=all" is received. This makes
Eclipse DSF assume the inferior resumed, although the inferior is still
suspended.

I tracked it down to the function mi_on_resume() in mi-interp.c and developed a
simple patch, that seems to work fine for me at least.

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

[Bug mi/18622] Erroneous "running" event while in suspended state messing up Eclipse DSF

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I'm not 100% sure but I think this was fixed a while ago.
mi_on_resume looks different now, and the "running" flag
is set in a completely different way.
Feel free to reopen if this is still an issue.

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