[Bug mi/25654] New: mi command "-exec-run" responding with an "async-output" record right after the "result-record"

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug mi/25654] New: mi command "-exec-run" responding with an "async-output" record right after the "result-record"

glaubitz at physik dot fu-berlin.de
https://sourceware.org/bugzilla/show_bug.cgi?id=25654

            Bug ID: 25654
           Summary: mi command "-exec-run" responding with an
                    "async-output" record right after the "result-record"
           Product: gdb
           Version: 8.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: yedidya.ep at gmail dot com
  Target Milestone: ---

Setup:
Build for windows as part of "MinGW_Gnu_8.3.0" distribution.
running command: gdb.exe --interpreter=mi3

commands and output:
    =thread-group-added,id="i1"
    ~"GNU gdb (GDB) 7.4\n"
    ~"Copyright (C) 2012 Free Software Foundation, Inc.\n"
    ~"License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to
change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by
law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
    ~"This GDB was configured as \"i686-pc-mingw32\".\nFor bug reporting
instructions, please see:\n"
    ~"<http://www.gnu.org/software/gdb/bugs/>.\n"
    (gdb)
--> -file-exec-and-symbols tests\\helloWorld.exe
    ^done
    (gdb)
--> -exec-run
    =thread-group-started,id="i1",pid="15216"
    =thread-created,id="1",group-id="i1"
    ~"[New Thread 15216.0x466c]\n"
    ^running
    *running,thread-id="all"
    (gdb)
    =thread-created,id="2",group-id="i1"
    ~"[New Thread 15216.0x4de0]\n"
    *running,thread-id="all"
   
=library-loaded,id="C:\\WINDOWS\\SysWOW64\\kernel32.dll",target-name="C:\\WINDOWS\\SysWOW64\\kernel32.dll",host-name="C:\\WINDOWS\\SysWOW64\\kernel32.dll",symbols-loaded="0",thread-group="i1"
   
=library-loaded,id="C:\\WINDOWS\\SysWOW64\\KernelBase.dll",target-name="C:\\WINDOWS\\SysWOW64\\KernelBase.dll",host-name="C:\\WINDOWS\\SysWOW64\\KernelBase.dll",symbols-loaded="0",thread-group="i1"
   
=library-loaded,id="C:\\WINDOWS\\SysWOW64\\msvcrt.dll",target-name="C:\\WINDOWS\\SysWOW64\\msvcrt.dll",host-name="C:\\WINDOWS\\SysWOW64\\msvcrt.dll",symbols-loaded="0",thread-group="i1"
    Hello, World! result is:8=thread-exited,id="2",group-id="i1"
    =thread-exited,id="1",group-id="i1"
    =thread-group-exited,id="i1",exit-code="0"
    *stopped,reason="exited-normally"
    (gdb)

According to the documentation in
"https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax":
GDB/MI Output should be: output → ( out-of-band-record )* [ result-record ]
"(gdb)" nl
however, in the above response for the "-exec-run" contain async-output
(*running,thread-id="all") right after the result record (^running)

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug mi/25654] mi command "-exec-run" responding with an "async-output" record right after the "result-record"

glaubitz at physik dot fu-berlin.de
https://sourceware.org/bugzilla/show_bug.cgi?id=25654

Yedidya <yedidya.ep at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|8.3                         |7.4

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