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. 81219e5358e6238d3810136690a0c0b2cd20955e


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  81219e5358e6238d3810136690a0c0b2cd20955e (commit)
      from  d4b38d2d057a5b8a35bc052e4f43b02b53c40f89 (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=81219e5358e6238d3810136690a0c0b2cd20955e

commit 81219e5358e6238d3810136690a0c0b2cd20955e
Author: Doug Evans <xdje42@gmail.com>
Date:   Sat Sep 13 21:44:00 2014 -0700

    New command queue-signal.
    
    If I want to change the signalled state of multiple threads
    it's a bit cumbersome to do with the "signal" command.
    What you really want is a way to set the signal state of the
    desired threads and then just do "continue".
    
    This patch adds a new command, queue-signal, to accomplish this.
    Basically "signal N" == "queue-signal N" + "continue".
    That's not precisely true in that "signal" can be used to inject
    any signal, including signals set to "nopass"; whereas "queue-signal"
    just queues the signal as if the thread stopped because of it.
    "nopass" handling is done when the thread is resumed which
    "queue-signal" doesn't do.
    
    One could add extra complexity to allow queue-signal to be used to
    deliver "nopass" signals like the "signal" command.  I have no current
    need for it so in the interests of incremental complexity, I have
    left such support out and just have the code flag an error if one
    tries to queue a nopass signal.
    
    gdb/ChangeLog:
    
    	* NEWS: Mention new "queue-signal" command.
    	* infcmd.c (queue_signal_command): New function.
    	(_initialize_infcmd): Add new queue-signal command.
    
    gdb/doc/ChangeLog:
    
    	* gdb.texinfo (Signaling): Document new queue-signal command.
    
    gdb/testsuite/ChangeLog:
    
    	* gdb.threads/queue-signal.c: New file.
    	* gdb.threads/queue-signal.exp: New file.

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

Summary of changes:
 gdb/ChangeLog                              |    6 ++
 gdb/NEWS                                   |    5 ++
 gdb/doc/ChangeLog                          |    4 +
 gdb/doc/gdb.texinfo                        |   31 +++++++--
 gdb/infcmd.c                               |   59 ++++++++++++++++-
 gdb/testsuite/ChangeLog                    |    5 ++
 gdb/testsuite/gdb.threads/queue-signal.c   |  102 ++++++++++++++++++++++++++++
 gdb/testsuite/gdb.threads/queue-signal.exp |   91 +++++++++++++++++++++++++
 8 files changed, 297 insertions(+), 6 deletions(-)
 create mode 100644 gdb/testsuite/gdb.threads/queue-signal.c
 create mode 100644 gdb/testsuite/gdb.threads/queue-signal.exp


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]