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. 6f259a235d01fe7b98c8ad6e8edc06d72074a14a


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  6f259a235d01fe7b98c8ad6e8edc06d72074a14a (commit)
      from  09dd9a6907f0929f2b634e57e68f11a008dfbf68 (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=6f259a235d01fe7b98c8ad6e8edc06d72074a14a

commit 6f259a235d01fe7b98c8ad6e8edc06d72074a14a
Author: Don Breazeal <donb@codesourcery.com>
Date:   Fri Oct 24 11:36:06 2014 -0700

    Follow-fork message printing improvements
    
    This commit modifies the code that prints attach and detach messages
    related to following fork and vfork.  The changes include using
    target_terminal_ours_for_output instead of target_terminal_ours,
    printing "vfork" instead of "fork" for all vfork-related messages,
    and using _() for the format strings of all of the messages.
    
    We also add a "detach" message for when a fork parent is detached.
    Previously in this case the only message was notification of attaching
    to the child.  We still do not print any messages when following the
    parent and detaching the child (the default).  The rationale for this
    is that from the user's perspective the new child was never attached.
    
    Note that all of these messages are only printed when 'verbose' is set
    or when debugging is turned on.
    
    The tests gdb.base/foll-fork.exp and gdb.base/foll-vfork.exp were
    modified to check for the new message.
    
    Tested on x64 Ubuntu Lucid, native only.
    
    gdb/ChangeLog:
    
    	* infrun.c (follow_fork_inferior): Update fork message printing
    	to use target_terminal_ours_for_output instead of
    	target_terminal_ours, to use _() for all format strings, to print
    	"vfork" instead of "fork" for vforks, and to add a detach message.
    	(handle_vfork_child_exec_or_exit): Update message printing to use
    	target_terminal_ours_for_output instead of target_terminal_ours, to
    	use _() for all format strings, and to fix some formatting.
    
    gdb/testsuite/ChangeLog:
    
    	* gdb.base/foll-fork.exp (test_follow_fork,
    	catch_fork_child_follow): Check for updated fork messages emitted
    	from infrun.c.
    	* gdb.base/foll-vfork.exp (vfork_parent_follow_through_step,
    	vfork_parent_follow_to_bp, vfork_and_exec_child_follow_to_main_bp,
    	vfork_and_exec_child_follow_through_step): Check for updated vfork
    	messages emitted from infrun.c.

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

Summary of changes:
 gdb/ChangeLog                         |   10 +++++
 gdb/infrun.c                          |   60 +++++++++++++++++++-------------
 gdb/testsuite/ChangeLog               |   10 +++++
 gdb/testsuite/gdb.base/foll-fork.exp  |   12 ++++--
 gdb/testsuite/gdb.base/foll-vfork.exp |    8 ++--
 5 files changed, 68 insertions(+), 32 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]