gdb and binutils branch master updated. 075c703382f5bed4ec0976dd11f3b5b694ce3cb1

[gary 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  075c703382f5bed4ec0976dd11f3b5b694ce3cb1 (commit)
       via  91b35fd05c777ffba9b1738711d470977779c687 (commit)
       via  b1ec390e096983dea311a853c412494a4991153e (commit)
       via  fd0ef3dda9fa7af181d059e4b3e26c17c1385c0d (commit)
       via  e0e6bcab5971ea4ad7c4f2efa5c8164c8383caf6 (commit)
       via  0d2f5c0791fda17ebbc503c5e7716fcb619318fc (commit)
       via  5df43998152f7096f8eed45c24a4fad5a3244d8b (commit)
       via  2437fd32f17cb11338949cff1fd0741e14ce1681 (commit)
      from  4805fc5533c158766d04f58af62bea884d624421 (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=075c703382f5bed4ec0976dd11f3b5b694ce3cb1

commit 075c703382f5bed4ec0976dd11f3b5b694ce3cb1
Author: Gary Benson <gbenson@redhat.com>
Date:   Tue Aug 5 16:18:51 2014 +0100

    Unify startup and option-parsing warnings
    
    Various warnings are emitted during startup and option-parsing using
    fprintf_unfiltered.  One warning is prefixed with the command name,
    the others are not.  This commit replaces these hardwired warnings
    with calls to warning.  It also sets warning_pre_print to prefix all
    warnings with the command name until option parsing is complete.
    
    gdb/ChangeLog:
    
    	* main.c (captured_main): Use warning during startup.
    	Prefix startup warning messages with command name.

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=91b35fd05c777ffba9b1738711d470977779c687

commit 91b35fd05c777ffba9b1738711d470977779c687
Author: Gary Benson <gbenson@redhat.com>
Date:   Tue Aug 5 16:12:01 2014 +0100

    Replace all usage errors with calls to error
    
    This commit replaces the hardwired fprintf/exit error handlers
    for usage errors with calls to error.
    
    gdb/ChangeLog:
    
    	* main.c (captured_main): Handle usage errors with error.

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

commit b1ec390e096983dea311a853c412494a4991153e
Author: Gary Benson <gbenson@redhat.com>
Date:   Mon Aug 4 14:44:56 2014 +0100

    Replace hardwired error handler in go32_create_inferior
    
    go32_create_inferior invokes a hardwired fprintf/exit error handler
    if v2loadimage fails.  I could find no reason for this other than that
    the block seems to have been copy-and-pasted from v2loadimage's
    manpage.  This commit replaces the hardwired handler with a call to
    error.
    
    gdb/ChangeLog:
    
    	* go32-nat.c (go32_create_inferior): Replace a fprintf/
    	exit pair with a call to error.  Wrap the message with _().

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

commit fd0ef3dda9fa7af181d059e4b3e26c17c1385c0d
Author: Gary Benson <gbenson@redhat.com>
Date:   Mon Aug 4 14:08:46 2014 +0100

    Replace hardwired error handler in captured_main
    
    If the requested interpreter cannot be set captured_main reports the
    error with a hardwired fprintf/exit pair.  A fprintf/exit pair on the
    previous line was replaced with a call to error in March 2003
    (https://sourceware.org/ml/gdb-patches/2003-03/msg00444.html) but I
    found no documentation as to why this particular hardwired handler
    was left untouched.  I was also unable to come up with a situation
    where error would not be suitable, so I have replaced it with a call
    to error.
    
    gdb/ChangeLog:
    
    	* main.c (captured_main): Replace a fprintf/exit
    	pair with a call to error.  Wrap the message with _().

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

commit e0e6bcab5971ea4ad7c4f2efa5c8164c8383caf6
Author: Gary Benson <gbenson@redhat.com>
Date:   Mon Aug 4 14:03:21 2014 +0100

    Replace hardwired error handlers in tui_initialize_io
    
    tui_initialize_io contains a pair of hardwired fprintf/exit error
    handlers.  I was unable to find any documentation as to why they're
    hardwired (the code appeared in a monolithic block back in 2001:
    https://sourceware.org/ml/gdb-patches/2001-07/msg00490.html) and I
    was also unable to come up with a situation where error would not
    be suitable, so I have replaced both handlers with calls to error.
    
    gdb/ChangeLog:
    
    	* tui/tui-io.c (tui_initialize_io): Replace two fprintf/exit
    	pairs with calls to error.  Wrap the message with _().

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0d2f5c0791fda17ebbc503c5e7716fcb619318fc

commit 0d2f5c0791fda17ebbc503c5e7716fcb619318fc
Author: Gary Benson <gbenson@redhat.com>
Date:   Tue Aug 5 13:27:49 2014 +0100

    Make warning usable earlier
    
    warning will crash if called before the first call to set_width.  This
    commit makes the warning usable from the moment gdb_stderr is set up.
    
    gdb/ChangeLog:
    
    	* utils.c (vwarning): Protect calls to target_terminal_ours
    	and wrap_here.

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

commit 5df43998152f7096f8eed45c24a4fad5a3244d8b
Author: Gary Benson <gbenson@redhat.com>
Date:   Tue Aug 5 13:25:48 2014 +0100

    Make error usable earlier
    
    error (and other exception-throwing functions) are callable from the
    first line of captured_main, but the exception printing code will
    crash if called before the first call to set_width.  This commit makes
    the exception printing code usable from the moment gdb_stderr is set
    up.
    
    gdb/ChangeLog:
    
    	* exceptions.c (print_flush): Protect calls to
    	target_terminal_ours and wrap_here.

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2437fd32f17cb11338949cff1fd0741e14ce1681

commit 2437fd32f17cb11338949cff1fd0741e14ce1681
Author: Gary Benson <gbenson@redhat.com>
Date:   Tue Aug 5 11:42:21 2014 +0100

    Make internal_vproblem always work
    
    internal_vproblem can be called (via malloc_failure) from almost the
    first line of captured_main, but it will crash if called before the
    first call to set_width.  This commit makes internal_vproblem work
    at any time.
    
    There are two parts to this.  If called before gdb_stderr is set up,
    internal_vproblem will fall back to printing the message on regular
    stderr and aborting.  If called after gdb_stderr is set up but before
    filtered printing is set up, internal_vproblem will operate as usual
    except that it can not query whether to quit and/or dump core so it
    defaults to doing both.
    
    gdb/ChangeLog:
    
    	* utils.h (filtered_printing_initialized): New declaration.
    	* utils.c (abort_with_message): New function.
    	(internal_vproblem): Use abort_with_message for first level
    	recursive internal problems, and if gdb_stderr is not set up.
    	Protect calls to target_terminal_ours, begin_line and query.

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

Summary of changes:
 gdb/ChangeLog    |   42 +++++++++++++++++++++++++++++
 gdb/exceptions.c |    7 +++-
 gdb/go32-nat.c   |   12 ++++----
 gdb/main.c       |   78 ++++++++++++++---------------------------------------
 gdb/tui/tui-io.c |   12 +++-----
 gdb/utils.c      |   54 ++++++++++++++++++++++++++++++-------
 gdb/utils.h      |    3 ++
 7 files changed, 125 insertions(+), 83 deletions(-)


hooks/post-receive
-- 
gdb and binutils