From: Yao Qi <yao@codesourcery.com>
To: Reini Urban <reini@cpanel.net>
Cc: <gdb-patches@sourceware.org>
Subject: Re: GDB 7.6.90 available for testing
Date: Fri, 10 Jan 2014 01:52:00 -0000 [thread overview]
Message-ID: <52CF51F7.3@codesourcery.com> (raw)
In-Reply-To: <52CD9682.2060805@cpanel.net>
On 01/09/2014 02:18 AM, Reini Urban wrote:
> FAIL: gdb.base/completion.exp: complete 'file ./gdb.base/complet' (timeout)
> FAIL: gdb.base/completion.exp: complete 'info func marke' (timeout)
> FAIL: gdb.base/completion.exp: complete 'set follow-fork-mode' (timeout)
> FAIL: gdb.base/completion.exp: field completion with invalid field (got
> interactive prompt)
> FAIL: gdb.base/longjmp.exp: next over longjmp(1)
> FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)
> FAIL: gdb.base/valgrind-infcall.exp: target remote for vgdb
> Running ./gdb.dwarf2/dw2-compressed.exp ...
> ERROR: remote_download to host of ./gdb.dwarf2/file1.txt to
> /home/rurban/Software/gdb-7.6.90/gdb/testsuite/gdb.dwarf2/file1.txt: cp:
> cannot stat './gdb.dwarf2/file1.txt': No such file or directory
> FAIL: gdb.dwarf2/dw2-compressed.exp: list func_cu1
> FAIL: gdb.dwarf2/dw2-filename.exp: interpreter-exec mi
> -file-list-exec-source-files
> FAIL: gdb.dwarf2/dw2-filename.exp: info sources
> ERROR: remote_download to host of ./gdb.dwarf2/file1.txt to
> /home/rurban/Software/gdb-7.6.90/gdb/testsuite/gdb.dwarf2/file1.txt: cp:
> cannot stat './gdb.dwarf2/file1.txt': No such file or directory
> FAIL: gdb.dwarf2/dw2-intercu.exp: list func_cu1
> Running ./gdb.dwarf2/dw2-intermix.exp ...
> ERROR: remote_download to host of ./gdb.dwarf2/file1.txt to
> /home/rurban/Software/gdb-7.6.90/gdb/testsuite/gdb.dwarf2/file1.txt: cp:
> cannot stat './gdb.dwarf2/file1.txt': No such file or directory
> FAIL: gdb.dwarf2/dw2-intermix.exp: list func_cul
> ERROR: remote_download to host of ./gdb.dwarf2/file1.txt to
> /home/rurban/Software/gdb-7.6.90/gdb/testsuite/gdb.dwarf2/file1.txt: cp:
> cannot stat './gdb.dwarf2/file1.txt': No such file or directory
> FAIL: gdb.dwarf2/dw2-producer.exp: list func_cu1
> ERROR: remote_download to host of ./gdb.dwarf2/file1.txt to
> /home/rurban/Software/gdb-7.6.90/gdb/testsuite/gdb.dwarf2/file1.txt: cp:
> cannot stat './gdb.dwarf2/file1.txt': No such file or directory
> FAIL: gdb.dwarf2/mac-fileno.exp: list func_cu1
> FAIL: gdb.fortran/array-element.exp: continue to breakpoint once again
> (the program exited)
> FAIL: gdb.mi/mi-var-rtti.exp: list children of s.public in
> type_update_when_use_rtti
> FAIL: gdb.mi/mi-var-rtti.exp: list children of s.ptr (without RTTI) in
> type_update_when_use_rtti
> FAIL: gdb.mi/mi-var-rtti.exp: list children of s.ptr.public (without
> RTTI) in type_update_when_use_rtti
> FAIL: gdb.python/py-prettyprint.exp: print ss
> FAIL: gdb.python/py-prettyprint.exp: print ssa[1]
> FAIL: gdb.python/py-prettyprint.exp: print ssa
> FAIL: gdb.python/py-prettyprint.exp: print arraystruct
> FAIL: gdb.python/py-prettyprint.exp: print ns2
> FAIL: gdb.python/py-prettyprint.exp: print x
> FAIL: gdb.python/py-prettyprint.exp: print cstring
> FAIL: gdb.python/py-prettyprint.exp: print estring
> FAIL: gdb.python/py-prettyprint.exp: print estring2
> FAIL: gdb.python/py-prettyprint.exp: print hint_error
> FAIL: gdb.python/py-prettyprint.exp: print c
> FAIL: gdb.python/py-prettyprint.exp: print nstype
> FAIL: gdb.python/py-prettyprint.exp: print nstype on one line
> ERROR: remote_download to host of ./gdb.python/py-prettyprint.py to
> /home/rurban/Software/gdb-7.6.90/gdb/testsuite/gdb.python/py-prettyprint.py:
> cp: cannot stat './gdb.python/py-prettyprint.py': No such file or directory
> FAIL: gdb.python/py-prettyprint.exp: print ss
> FAIL: gdb.python/py-prettyprint.exp: print ssa[1]
> FAIL: gdb.python/py-prettyprint.exp: print ssa
> FAIL: gdb.python/py-prettyprint.exp: print arraystruct
> FAIL: gdb.python/py-prettyprint.exp: print cps
> FAIL: gdb.python/py-prettyprint.exp: print cpss
> FAIL: gdb.python/py-prettyprint.exp: print cpssa[0]
> FAIL: gdb.python/py-prettyprint.exp: print cpssa[1]
> FAIL: gdb.python/py-prettyprint.exp: print cpssa
> FAIL: gdb.python/py-prettyprint.exp: print sss
> FAIL: gdb.python/py-prettyprint.exp: print ref
> FAIL: gdb.python/py-prettyprint.exp: print derived
> FAIL: gdb.python/py-prettyprint.exp: print ns
> FAIL: gdb.python/py-prettyprint.exp: print ns
> FAIL: gdb.python/py-prettyprint.exp: print ns
> FAIL: gdb.python/py-prettyprint.exp: print ns2
> FAIL: gdb.python/py-prettyprint.exp: print x
> FAIL: gdb.python/py-prettyprint.exp: print cstring
> FAIL: gdb.python/py-prettyprint.exp: print estring
> FAIL: gdb.python/py-prettyprint.exp: print estring2
> FAIL: gdb.python/py-prettyprint.exp: print hint_error
> FAIL: gdb.python/py-prettyprint.exp: print c
> FAIL: gdb.python/py-prettyprint.exp: print nstype
> FAIL: gdb.python/py-prettyprint.exp: print nstype on one line
> ERROR: remote_download to host of ./gdb.python/py-prettyprint.py to
> /home/rurban/Software/gdb-7.6.90/gdb/testsuite/gdb.python/py-prettyprint.py:
> cp: cannot stat './gdb.python/py-prettyprint.py': No such file or directory
> FAIL: gdb.python/py-prettyprint.exp: info locals
> FAIL: gdb.python/py-prettyprint.exp: print ss enabled #1
> FAIL: gdb.python/py-prettyprint.exp: python disable_lookup_function ()
> FAIL: gdb.python/py-prettyprint.exp: python enable_lookup_function ()
> FAIL: gdb.python/py-prettyprint.exp: print ss enabled #2
I can reproduce most of these fails, quoted above, (on amd64 ubuntu
machine) in an in-tree build and test. Looks we need to tweak
testsuite/lib/*.exp files to support in-tree build well.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-01-10 1:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 10:14 Joel Brobecker
2014-01-08 18:18 ` Reini Urban
2014-01-09 2:46 ` Joel Brobecker
2014-01-09 17:07 ` Tom Tromey
2014-01-10 4:25 ` Joel Brobecker
2014-01-10 1:52 ` Yao Qi [this message]
2014-01-09 18:27 ` Regressions on s390x RHEL-6.5 (was: Re: GDB 7.6.90 available for testing) Sergio Durigan Junior
2014-01-11 8:56 ` GDB 7.6.90 available for testing Eli Zaretskii
2014-01-13 17:33 ` Eli Zaretskii
2014-01-13 17:51 ` Pedro Alves
2014-01-13 18:28 ` Eli Zaretskii
2014-01-13 18:44 ` Pedro Alves
2014-01-13 18:50 ` Eli Zaretskii
2014-01-13 19:15 ` Eli Zaretskii
2014-01-13 19:53 ` Pedro Alves
2014-01-13 20:33 ` Eli Zaretskii
2014-01-15 16:33 ` Eli Zaretskii
2014-01-13 10:29 ` Ricard Wanderlof
2014-01-13 10:37 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CF51F7.3@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=reini@cpanel.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).