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. 470e2f4e300e5f84b1c35070df43d69b501e0b91


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  470e2f4e300e5f84b1c35070df43d69b501e0b91 (commit)
      from  ae527cd876fe35de72d876d3484e194ccc66232f (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=470e2f4e300e5f84b1c35070df43d69b501e0b91

commit 470e2f4e300e5f84b1c35070df43d69b501e0b91
Author: Luis Machado <lgustavo@codesourcery.com>
Date:   Tue Nov 18 11:16:37 2014 -0200

    I caught a few mingw32-specific failures for some of the gdb.reverse
    tests.
    
    FAIL: gdb.reverse/consecutive-precsave.exp: reload precord save file
    FAIL: gdb.reverse/finish-precsave.exp: reload precord save file
    FAIL: gdb.reverse/until-precsave.exp: reload core file
    FAIL: gdb.reverse/watch-precsave.exp: reload core file
    FAIL: gdb.reverse/step-precsave.exp: reload core file
    FAIL: gdb.reverse/break-precsave.exp: reload precord save file
    FAIL: gdb.reverse/sigall-precsave.exp: reload precord save file
    
    They happen for two reasons.
    
    - mingw32 does not define SIGTRAP, so upon recording a core file, the
    signal information will be missing, which in turn causes GDB to not
    display the stopping signal when it loads the same core file.  An
    earlier message warns about this:
    
    "warning: Signal SIGTRAP does not exist on this system."
    
    - The testcase is crafted in a way that expects a pattern of the
    stopping signal message instead of a successful core file read message.
    
    The following patch fixes this by changing the old pattern to a more
    reasonable one, while still ignoring the fact that mingw32-based GDB
    does not record a SIGTRAP in a core file because it does not define
    it.
    
    gdb/testsuite/
    
    2014-11-18  Luis Machado  <lgustavo@codesourcery.com>
    
    	* gdb.reverse/break-precsave: Expect completion message for
    	core file reads.
    	* gdb.reverse/consecutive-precsave.exp: Likewise.
    	* gdb.reverse/finish-precsave.exp: Likewise.
    	* gdb.reverse/i386-precsave.exp: Likewise.
    	* gdb.reverse/machinestate-precsave.exp: Likewise.
    	* gdb.reverse/sigall-precsave.exp: Likewise.
    	* gdb.reverse/solib-precsave.exp: Likewise.
    	* gdb.reverse/step-precsave.exp: Likewise.
    	* gdb.reverse/until-precsave.exp: Likewise.
    	* gdb.reverse/watch-precsave.exp: Likewise.

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

Summary of changes:
 gdb/testsuite/ChangeLog                            |   14 ++++++++++++++
 gdb/testsuite/gdb.reverse/break-precsave.exp       |    2 +-
 gdb/testsuite/gdb.reverse/consecutive-precsave.exp |    2 +-
 gdb/testsuite/gdb.reverse/finish-precsave.exp      |    2 +-
 gdb/testsuite/gdb.reverse/i386-precsave.exp        |    2 +-
 .../gdb.reverse/machinestate-precsave.exp          |    2 +-
 gdb/testsuite/gdb.reverse/sigall-precsave.exp      |    2 +-
 gdb/testsuite/gdb.reverse/solib-precsave.exp       |    2 +-
 gdb/testsuite/gdb.reverse/step-precsave.exp        |    2 +-
 gdb/testsuite/gdb.reverse/until-precsave.exp       |    2 +-
 gdb/testsuite/gdb.reverse/watch-precsave.exp       |    2 +-
 11 files changed, 24 insertions(+), 10 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]