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. 0b10be4faf97396c88746f932b55bc3d2fb2d907


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  0b10be4faf97396c88746f932b55bc3d2fb2d907 (commit)
      from  6e03f3da7df9ec3c2852d50d4c4039dc80d606f6 (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=0b10be4faf97396c88746f932b55bc3d2fb2d907

commit 0b10be4faf97396c88746f932b55bc3d2fb2d907
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Sun Feb 16 21:49:40 2014 +0100

    Fix "ERROR: no fileid for" in the testsuite.
    
    If GDB has crashed then gdb_spawn_id still exists (although it does not work).
    So my patch does not change anything.  And also currently it will leave the
    stale gdbserver running anyway.
    
    In general if gdb_spawn_id does not exist then send_gdb + gdb_expect just do
    not make sense anyway.  So this patch just prevents the error in such case.
    
    The killing of stale gdbserver could be improved multiple ways (also as
    suggested by Pedro in the original thread) but that is IMO outside of the
    scope of this patch.  Apparently if there is no good response from GDB then
    gdb_finish() should try to call gdb_start just to kill that gdbserver, IIUC.
    
    gdb/testsuite/
    2014-02-16  Jan Kratochvil  <jan.kratochvil@redhat.com>
    
    	Fix "ERROR: no fileid for" in the testsuite.
    	* lib/gdb.exp (gdb_finish): Check gdb_spawn_id.
    
    Message-ID: <20140206205814.GA18495@host2.jankratochvil.net>

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

Summary of changes:
 gdb/testsuite/ChangeLog   |    5 +++++
 gdb/testsuite/lib/gdb.exp |    3 ++-
 2 files changed, 7 insertions(+), 1 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]