gdb and binutils branch master updated. 5a5095892cba5d6c8f3f73bf2f804870b222d759

[palves at sourceware dot 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, master has been updated
       via  5a5095892cba5d6c8f3f73bf2f804870b222d759 (commit)
      from  5cf709fcef254c3b88db769645afe1ae4e10849c (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=5a5095892cba5d6c8f3f73bf2f804870b222d759

commit 5a5095892cba5d6c8f3f73bf2f804870b222d759
Author: Pedro Alves <palves@redhat.com>
Date:   Tue Oct 22 15:02:28 2013 +0100

    remote: Map invalid signal numbers to GDB_SIGNAL_UNKNOWN.
    
    I realized that remote.c is not validating input here.  Currently, if
    a remote stub sends in an invalid signal number (or put another way,
    if a future stub sends a new signal an old GDB doesn't know about),
    GDB will do out of bounds accesses in the
    signal_pass/signal_stop/signal_program arrays.  It'll probably be a
    long while before we add another signal number (and buggy stubs should
    just be fixed), but can't hurt to be defensive.
    
    Tested on x86_64 Fedora 17, native gdbserver.
    
    gdb/
    2013-10-22  Pedro Alves  <palves@redhat.com>
    
    	* remote.c (remote_parse_stop_reply) <'T'/'S'/'X' replies>: Map
    	invalid signal numbers to GDB_SIGNAL_UNKNOWN.

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

Summary of changes:
 gdb/remote.c |   18 ++++++++++++++----
 1 files changed, 14 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
gdb and binutils