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. ecebef6a9acbca2f98e1ed64b986d792c6933ec5


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  ecebef6a9acbca2f98e1ed64b986d792c6933ec5 (commit)
      from  ecdf850f8515140a3c15bc8ca55172276bcc914d (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=ecebef6a9acbca2f98e1ed64b986d792c6933ec5

commit ecebef6a9acbca2f98e1ed64b986d792c6933ec5
Author: Maciej W. Rozycki <macro@codesourcery.com>
Date:   Fri Mar 21 23:51:16 2014 +0000

    gdb.threads/thread-specific.exp: Fix uninitialized variable references
    
    This fixes:
    
    FAIL: gdb.threads/thread-specific.exp: continue to thread-specific breakpoint (timeout)
    ERROR: tcl error sourcing .../gdb/testsuite/gdb.threads/thread-specific.exp.
    ERROR: can't read "this_breakpoint": no such variable
        while executing
    "gdb_test_multiple "info breakpoint $this_breakpoint" "info on bp" {
        -re ".*stop only in thread (\[0-9\]*).*$gdb_prompt $" {
            set this_thread $expe..."
        (file ".../gdb/testsuite/gdb.threads/thread-specific.exp" line 108)
        invoked from within
    "source .../gdb/testsuite/gdb.threads/thread-specific.exp"
        ("uplevel" body line 1)
        invoked from within
    "uplevel #0 source .../gdb/testsuite/gdb.threads/thread-specific.exp"
        invoked from within
    "catch "uplevel #0 source $test_file_name""
    
    and then:
    
    FAIL: gdb.threads/thread-specific.exp: continue to thread-specific breakpoint (timeout)
    UNTESTED: gdb.threads/thread-specific.exp: info on bp
    ERROR: tcl error sourcing .../gdb/testsuite/gdb.threads/thread-specific.exp.
    ERROR: can't read "this_thread": no such variable
        while executing
    "gdb_test {print $_thread} ".* = $this_thread" "thread var at break""
        (file ".../gdb/testsuite/gdb.threads/thread-specific.exp" line 119)
        invoked from within
    "source .../gdb/testsuite/gdb.threads/thread-specific.exp"
        ("uplevel" body line 1)
        invoked from within
    "uplevel #0 source .../gdb/testsuite/gdb.threads/thread-specific.exp"
        invoked from within
    "catch "uplevel #0 source $test_file_name""
    
    Final results:
    
    FAIL: gdb.threads/thread-specific.exp: continue to thread-specific breakpoint (timeout)
    UNTESTED: gdb.threads/thread-specific.exp: info on bp
    UNTESTED: gdb.threads/thread-specific.exp: thread var at break
    
    Of course the first failure best wasn't there, but failing that the script
    shouldn't crash.
    
    	* gdb.threads/thread-specific.exp: Handle the lack of usable
    	$this_breakpoint and $this_thread.

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

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