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/17096] async support breaks remote debugging on Windows


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

--- Comment #15 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, gdb-7.8-branch has been updated
       via  5bbc46815600d34fe7e5f3b8cda4bad0a70e95ad (commit)
      from  780400a0c9f76242dd7f0b3caf6c22947e909e88 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5bbc46815600d34fe7e5f3b8cda4bad0a70e95ad

commit 5bbc46815600d34fe7e5f3b8cda4bad0a70e95ad
Author: Pedro Alves <palves@redhat.com>
Date:   Mon Jul 7 19:06:35 2014 +0100

    PR gdb/17096: async support breaks remote debugging on Windows

    On Windows, with "maint set target-async on" (the default since
    a09dd441), Ctrl-C fails to stop a remote target.

    With maint target-async on, the SIGINT signal handler doesn't send the
    remote interrupt request immediately.  Instead, it marks an async
    handler as ready, and then the main event loop wakes up and notices
    that the SIGINT async signal handler token was set, and calls the
    corresponding event handler, which sends the remote interrupt request.

    On POSIX-like systems, the SIGINT signal makes the select/poll in the
    main event loop wake up / return with EINTR.  However, on Windows,
    signal handlers run on a separate thread, and Windows doesn't really
    have a concept of EINTR.  So, just marking the async handler
    (effectively just setting a flag) does not wake up gdb_select.
    Instead, we need to call gdb_call_async_signal_handler from the signal
    handler.  The Windows version (in mingw-hdep.c) sets a Windows event
    that gdb_select's WaitForMultipleObjects is waiting for.

    Confirmed that with this, Ctrl-C interrupts the remote target on
    Windows.  Also regression tested on x86_64 Fedora 20 against
    GDBserver.

    gdb/
    2014-07-07  Pedro Alves  <palves@redhat.com>

        gdb/17096
        * remote.c (async_handle_remote_sigint)
        (async_handle_remote_sigint_twice): Call
        gdb_call_async_signal_handler instead of
        mark_async_signal_handler.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog |    8 ++++++++
 gdb/remote.c  |    7 +++++--
 2 files changed, 13 insertions(+), 2 deletions(-)

-- 
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]