This is the mail archive of the gdb-cvs@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]

gdb and binutils branch master updated. b2ee242b93e9580406e03abb18ff969de7de1976


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, master has been updated
       via  b2ee242b93e9580406e03abb18ff969de7de1976 (commit)
      from  3510a7b805f8ad1345b9d2671a21a40a09d9f2a2 (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=b2ee242b93e9580406e03abb18ff969de7de1976

commit b2ee242b93e9580406e03abb18ff969de7de1976
Author: Pedro Alves <palves@redhat.com>
Date:   Mon Jul 7 17:51:04 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>
    
    	* 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 |    7 +++++++
 gdb/remote.c  |    7 +++++--
 2 files changed, 12 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gdb and binutils


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