public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Andreas Krebbel <Andreas.Krebbel@de.ibm.com>
To: gdb-testers@sourceware.org
Subject: GNU gdb (GDB) 7.8.50.20140723-cvs s390x-ibm-linux-gnu GIT commit: e294541cdab0373f6097862de1068cc985e7e242
Date: Wed, 23 Jul 2014 01:38:00 -0000	[thread overview]
Message-ID: <201407230138.s6N1cTfb023345@d06av09.portsmouth.uk.ibm.com> (raw)

Test Run By dailybuild on Wed Jul 23 03:27:57 2014
Native configuration is s390x-ibm-linux-gnu

		=== gdb tests ===

Schedule of variations:
    unix

FAIL: gdb.ada/O2_float_param.exp: frame
FAIL: gdb.ada/array_return.exp: value printed by finish of Create_Small
FAIL: gdb.ada/array_return.exp: value printed by finish of Create_Large
FAIL: gdb.ada/array_return.exp: value printed by finish of Create_Small_Float_Vector
FAIL: gdb.ada/dyn_arrayidx.exp: compilation foo.adb
FAIL: gdb.ada/lang_switch.exp: backtrace
FAIL: gdb.ada/mi_task_arg.exp: -stack-list-arguments 1
FAIL: gdb.ada/operator_bp.exp: break "+"
FAIL: gdb.ada/operator_bp.exp: break "-"
FAIL: gdb.ada/operator_bp.exp: break "mod"
FAIL: gdb.ada/tagged.exp: ptype obj
FAIL: gdb.base/call-sc.exp: value foo returned; return call-sc-tld
FAIL: gdb.base/dfp-test.exp: Correct _Decimal128 return value from called function.
FAIL: gdb.base/longjmp.exp: next over longjmp(1)
FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)
gdb compile failed, cc1: error: '-fsplit-stack' is not supported by this compiler configuration
gdb compile failed, /gdb/testsuite/gdb.base/stap-probe.c:43:2: error: #error "not using SystemTap v3 probes"
 #error "not using SystemTap v3 probes"
  ^
ERROR: Process no longer exists
UNRESOLVED: gdb.base/valgrind-db-attach.exp: attach to debugger
FAIL: gdb.cp/annota2.exp: watch triggered on a.x (timeout)
FAIL: gdb.cp/annota2.exp: annotate-quit
FAIL: gdb.cp/inherit.exp: print g_vD
FAIL: gdb.cp/inherit.exp: print g_vE
FAIL: gdb.cp/virtbase.exp: print *this
FAIL: gdb.cp/virtbase.exp: print *(D *) e
FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
FAIL: gdb.cp/vla-cxx.exp: print vla
FAIL: gdb.cp/vla-cxx.exp: print vlaref
FAIL: gdb.cp/vla-cxx.exp: print vlaref2
FAIL: gdb.cp/vla-cxx.exp: print c
FAIL: gdb.dwarf2/dw2-anon-mptr.exp: ptype crash
FAIL: gdb.dwarf2/implptrpiece.exp: print/d p[-1]
FAIL: gdb.dwarf2/member-ptr-forwardref.exp: ptype c
FAIL: gdb.fortran/array-element.exp: continue to breakpoint once again (the program exited)
FAIL: gdb.fortran/array-element.exp: print the second element of array a
FAIL: gdb.gdb/selftest.exp: unknown source line (after next over lim_at_start initialization)
FAIL: gdb.gdb/selftest.exp: step into xmalloc call
gdb compile failed, default_target_compile: Can't find gccgo.
gdb compile failed, default_target_compile: Can't find gccgo.
gdb compile failed, default_target_compile: Can't find gccgo.
gdb compile failed, default_target_compile: Can't find gccgo.
gdb compile failed, default_target_compile: Can't find gccgo.
gdb compile failed, default_target_compile: Can't find gccgo.
gdb compile failed, default_target_compile: Can't find gccgo.
gdb compile failed, default_target_compile: Can't find gccgo.
gdb compile failed, default_target_compile: Can't find gccgo.
FAIL: gdb.java/jmain.exp: compilation jmain.java
FAIL: gdb.java/jmisc.exp: compilation jmisc.java
FAIL: gdb.java/jnpe.exp: compilation jnpe.java
FAIL: gdb.java/jprint.exp: compilation jprint.java
FAIL: gdb.mi/mi-watch-nonstop.exp: delete watchpoint
FAIL: gdb.mi/pr11022.exp: data-write-memory-bytes &x "01": watchpoint hit 2 (unknown output after running)
FAIL: gdb.modula2/unbounded-array.exp: print unbounded array contents
FAIL: gdb.python/py-framefilter.exp: info frame filter before setting priority
FAIL: gdb.python/py-framefilter.exp: info frame filter after setting priority
FAIL: gdb.python/py-framefilter.exp: info frame filter before disable frame filter
FAIL: gdb.python/py-framefilter.exp: info frame filter after disable frame filter
FAIL: gdb.python/py-framefilter.exp: info frame filter after reenabling frame filter
FAIL: gdb.python/py-value-cc.exp: u's second field via field
FAIL: gdb.server/server-kill.exp: tstatus
FAIL: gdb.stabs/gdb11479.exp: Inspect t in test2 forced_stabs
FAIL: gdb.stabs/gdb11479.exp: Inspect t in test forced_stabs
FAIL: gdb.threads/step-over-trips-on-watchpoint.exp: no thread-specific bp: next: next
FAIL: gdb.trace/entry-values.exp: bt (1) (pattern 1)
FAIL: gdb.trace/entry-values.exp: bt (2) (pattern 1)
FAIL: gdb.trace/tfile.exp: tfind 0 on trace file
gdb compile failed, gcc: error: /gdb/testsuite/../gdbserver/libinproctrace.so: No such file or directory

		=== gdb Summary ===

# of expected passes		24834
# of unexpected failures	53
# of unexpected successes	1
# of expected failures		35
# of known failures		56
# of unresolved testcases	1
# of untested testcases		24
# of unsupported tests		88
/gdb/testsuite/../../gdb/gdb version  7.8.50.20140723-cvs -nw -nx -data-directory /gdb/testsuite/../data-directory 

PATH=/bigdisk/build-system/arena/20140722/gcc-head/install-s390x-default/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/dailybuild/bin

GCC Version

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/bigdisk/build-system/arena/20140722/gcc-head/install-s390x-default/bin/../libexec/gcc/s390x-ibm-linux-gnu/4.10.0/lto-wrapper
Target: s390x-ibm-linux-gnu
Configured with: /bigdisk/build-system/arena/20140722/gcc-head/src/configure --prefix=/bigdisk/build-system/arena/20140722/gcc-head/install-s390x-default --enable-shared --with-system-zlib --enable-threads=posix --enable-__cxa_atexit --enable-checking --enable-languages=c,c++,objc,obj-c++,fortran --with-mode=zarch
Thread model: posix
gcc version 4.10.0 20140722 (experimental) (GCC) 


                 reply	other threads:[~2014-07-23  1:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201407230138.s6N1cTfb023345@d06av09.portsmouth.uk.ibm.com \
    --to=andreas.krebbel@de.ibm.com \
    --cc=gdb-testers@sourceware.org \
    /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).