gdb and binutils branch master updated. 754dd2b00f2bd3f2d7aaacdb27375bc6faf1458e

[qiyao 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  754dd2b00f2bd3f2d7aaacdb27375bc6faf1458e (commit)
       via  f90183d7e31b335b8a6048e46805509dc56332a4 (commit)
       via  bf40a6078fd5bc24f54aaa1ca2bf44fa95b57c69 (commit)
      from  052ca3707367a7f1fae462a45c56e8e50fe3b98e (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=754dd2b00f2bd3f2d7aaacdb27375bc6faf1458e

commit 754dd2b00f2bd3f2d7aaacdb27375bc6faf1458e
Author: Yao Qi <yao@codesourcery.com>
Date:   Wed Oct 8 11:25:31 2014 +0800

    Enable qTStatus packet in case it is disabled
    
    Nowadays, we are using command "tstatus" to send a packet to GDBserver
    in order to check the connection.  However, on the target doesn't
    support tracepoint, the following error is emitted before sending any
    packet to GDBserver.
    
    tstatus^M
    Trace can not be run on this target.^M
    (gdb) FAIL: gdb.server/server-kill.exp: tstatus
    
    qTStatus is disabled after receiving the empty reply during connecting
    to the remote target.  When the test executes command "tstatus" again,
    remote_get_trace_status returns -1 at the very beginning, and no RSP
    packet is sent out.
    
    This patch is to enable qTStatus packet again.
    
    gdb/testsuite:
    
    2014-10-11  Yao Qi  <yao@codesourcery.com>
    
    	* gdb.server/server-kill.exp: Execute command
    	"set remote trace-status-packet on" before "tstatus".

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

commit f90183d7e31b335b8a6048e46805509dc56332a4
Author: Yao Qi <yao@codesourcery.com>
Date:   Tue Sep 30 21:08:15 2014 +0800

    Get GDBserver pid on remote target
    
    Hi,
    We see the following fail in the real remote testing...
    
    (gdb) Executing on target: kill -9 29808    (timeout = 300)
    spawn [open ...]^M
    sh: 1: kill: No such process
    
    The test tries to kill gdbserver in this way:
    
    set server_pid [exp_pid -i [board_info target fileid]]
    remote_exec target "kill -9 $server_pid"
    
    in native testing, we'll get the pid of spawned gdbserver, however, in
    remote testing, we'll get the pid of ssh session, since we start
    gdbserver on the remote target through ssh.  The pid on build doesn't
    exist on target.
    
    In this patch, we tweak server-kill.c to get the parent pid, which is
    the pid of GDBserver.  GDB gets it and kill GDBserver on target.
    
    gdb/testsuite:
    
    2014-10-11  Yao Qi  <yao@codesourcery.com>
    
    	* gdb.server/server-kill.c: Include sys/types.h and unistd.h.
    	(main): Call getppid.
    	* gdb.server/server-kill.exp: Set breakpoint on line "i = 0;"
    	and continue to it.  Read variable "server_pid".

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

commit bf40a6078fd5bc24f54aaa1ca2bf44fa95b57c69
Author: Yao Qi <yao@codesourcery.com>
Date:   Wed Oct 8 10:04:22 2014 +0800

    Clean up server-kill.exp
    
    This patch is to remove some lines which looks unnecessary.  These
    lines were added when server-kill.exp was added.  In the version 1,
    https://sourceware.org/ml/gdb-patches/2013-03/msg00691.html the test
    calls runto_main and delete breakpoint on main,
    
    +if ![runto_main] {
    +    return -1
    +}
    +
    +# Otherwise the breakpoint at 'main' would not cause insert
    breakpoints during
    +# first step.
    +delete_breakpoints
    
    However, in the version 2
    https://sourceware.org/ml/gdb-patches/2013-03/msg00854.html runto_main
    is removed but delete_breakpoints is still there.  AFAICS, the line of
    delete_breakpoints can be removed too.
    
    gdb/testsuite:
    
    2014-10-11  Yao Qi  <yao@codesourcery.com>
    
    	* gdb.server/server-kill.exp: Remove "delete_breakpoints".

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

Summary of changes:
 gdb/testsuite/ChangeLog                  |   16 ++++++++++++++++
 gdb/testsuite/gdb.server/server-kill.c   |   10 +++++++++-
 gdb/testsuite/gdb.server/server-kill.exp |   25 +++++++++++++++++++++----
 3 files changed, 46 insertions(+), 5 deletions(-)


hooks/post-receive
-- 
gdb and binutils