This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/18077] New: Using -exec-run with mi-async on results in synchronous execution


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

            Bug ID: 18077
           Summary: Using -exec-run with mi-async on results in
                    synchronous execution
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simon.marchi at ericsson dot com

Using this simple test program:

    int main()
    {
        for (;;);
        return 0;
    }

And trying these commands:

    $ gdb -nx -i mi a.out
    -gdb-set mi-async on
    -exec-run
    -exec-interrupt --all  <--- It doesn't work, even though it should since we
are in mi-async on mode.


I traced the root of the problem to this line:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/mi/mi-main.c;h=7412f7d8a553ca6739da1480c2e84572f38a8e78;hb=HEAD#l493

At this point, the linux-native run target is not pushed yet. mi_async_p ends
up calling tdefault_can_async, which returns false, so we don't execute
asynchronously.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]