gdb and binutils branch master updated. 5de51581685123bedd8160aec9a660e85e7a8b73

[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  5de51581685123bedd8160aec9a660e85e7a8b73 (commit)
      from  739cb10c0ecd53524e937f1d52518a8eebc3d359 (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=5de51581685123bedd8160aec9a660e85e7a8b73

commit 5de51581685123bedd8160aec9a660e85e7a8b73
Author: Pedro Alves <palves@redhat.com>
Date:   Thu Nov 28 15:44:58 2013 +0000

    get_prev_frame, UNWIND_NULL_ID -> UNWIND_OUTERMOST
    
    - The UNWIND_NULL_ID check in get_prev_frame_1 used to really be
      against null_frame_id, back before we had outer_frame_id.  We didn't
      have UNWIND_OUTERMOST when outer_frame_id was added, but we do now,
      and it's more accurate.
    
    - It used to be necessary to check for the sentinel frame explicitly
      because that uses null_frame_id for frame id.  Since no other frame
      can have that id nowadays (it's asserted by compute_frame_id), we
      don't need that explicit check.
    
    Tested on x86_64 Fedora 17.
    
    gdb/
    2013-11-28  Pedro Alves  <palves@redhat.com>
    
    	* frame.c (get_prev_frame_1): If the frame id is outer_frame_id,
    	set the unwind stop reason to UNWIND_OUTERMOST, not
    	UNWIND_NULL_ID.  Remove explicit check for sentinel frame.

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

Summary of changes:
 gdb/ChangeLog |    6 ++++++
 gdb/frame.c   |   11 +++++------
 2 files changed, 11 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
gdb and binutils