public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: Andreas Krebbel <krebbel@linux.vnet.ibm.com> To: gdb-testers@sourceware.org Subject: GNU gdb (GDB) 7.9.50.20150508-cvs s390x-ibm-linux-gnu GIT commit: Date: Fri, 08 May 2015 11:03:00 -0000 [thread overview] Message-ID: <201505081103.t48B326m032728@d06av09.portsmouth.uk.ibm.com> (raw) Test Run By dailybuild on Fri May 8 12:49:52 2015 Native configuration is s390x-ibm-linux-gnu === gdb tests === Schedule of variations: unix 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/mi_task_arg.exp: -stack-list-arguments 1 FAIL: gdb.ada/ptype_tagged_param.exp: ptype s FAIL: gdb.ada/ref_param.exp: frame argument value printed FAIL: gdb.ada/set_pckd_arr_elt.exp: continue to update_small FAIL: gdb.ada/tagged.exp: ptype obj FAIL: gdb.base/async-shell.exp: process stopped (timeout) FAIL: gdb.base/call-sc.exp: value foo returned; return call-sc-tld gdb compile failed, /gdb/testsuite/gdb.base/coredump-filter.c: In function 'main': /gdb/testsuite/gdb.base/coredump-filter.c:56:33: error: 'MADV_DONTDUMP' undeclared (first use in this function) i = madvise (dont_dump, size, MADV_DONTDUMP); ^ /gdb/testsuite/gdb.base/coredump-filter.c:56:33: note: each undeclared identifier is reported only once for each function it appears in FAIL: gdb.base/dfp-test.exp: Correct _Decimal128 return value from called function. ERROR: Process no longer exists UNRESOLVED: gdb.base/interrupt.exp: process is alive FAIL: gdb.base/longjmp.exp: next over longjmp(1) FAIL: gdb.base/longjmp.exp: next over call_longjmp (2) 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.base/watch_thread_num.exp: Watchpoint on shared variable FAIL: gdb.base/watch_thread_num.exp: info breakpoint shows watchpoint is thread-specific FAIL: gdb.base/watch_thread_num.exp: Watchpoint triggered iteration 1 (timeout) FAIL: gdb.base/watch_thread_num.exp: Check thread that triggered iteration 1 (timeout) FAIL: gdb.base/watch_thread_num.exp: Watchpoint triggered iteration 2 (timeout) FAIL: gdb.base/watch_thread_num.exp: Check thread that triggered iteration 2 (timeout) FAIL: gdb.base/watch_thread_num.exp: Watchpoint triggered iteration 3 (timeout) FAIL: gdb.base/watch_thread_num.exp: Check thread that triggered iteration 3 (timeout) FAIL: gdb.base/watch_thread_num.exp: Watchpoint triggered iteration 4 (timeout) FAIL: gdb.base/watch_thread_num.exp: Check thread that triggered iteration 4 (timeout) FAIL: gdb.base/watch_thread_num.exp: Watchpoint triggered iteration 5 (timeout) FAIL: gdb.base/watch_thread_num.exp: Check thread that triggered iteration 5 (timeout) FAIL: gdb.compile/compile-setjmp.exp: compile file -r FAIL: gdb.compile/compile-setjmp.exp: p done 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/no-dmgl-verbose.exp: setting breakpoint at 'f(std::string)' 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/library-module.exp: print var_i in lib FAIL: gdb.fortran/library-module.exp: print var_i in main FAIL: gdb.go/methods.exp: setting breakpoint at main.T.Foo FAIL: gdb.go/methods.exp: setting breakpoint at (*main.T).Bar FAIL: gdb.java/jprint.exp: single argument call FAIL: gdb.java/jprint.exp: double argument call FAIL: gdb.java/jprint.exp: virtual fn call FAIL: gdb.java/jprint.exp: inherited static call FAIL: gdb.java/jprint.exp: inherited virtual fn call 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.opt/inline-bt.exp: continue to bar (1) FAIL: gdb.opt/inline-bt.exp: backtrace from bar (1) FAIL: gdb.opt/inline-bt.exp: continue to bar (2) FAIL: gdb.opt/inline-bt.exp: backtrace from bar (2) FAIL: gdb.opt/inline-bt.exp: continue to bar (3) FAIL: gdb.opt/inline-bt.exp: backtrace from bar (3) FAIL: gdb.opt/inline-cmds.exp: continue to bar (1) FAIL: gdb.opt/inline-cmds.exp: backtrace from bar (1) FAIL: gdb.opt/inline-cmds.exp: continue to bar (2) FAIL: gdb.opt/inline-cmds.exp: backtrace from bar (2) FAIL: gdb.opt/inline-cmds.exp: continue to marker FAIL: gdb.opt/inline-cmds.exp: backtrace from marker FAIL: gdb.opt/inline-cmds.exp: step into finish marker FAIL: gdb.opt/inline-locals.exp: continue to bar (1) FAIL: gdb.opt/inline-locals.exp: continue to bar (2) FAIL: gdb.opt/inline-locals.exp: backtrace from bar (2) FAIL: gdb.opt/inline-locals.exp: continue to bar (3) FAIL: gdb.opt/inline-locals.exp: backtrace from bar (3) 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 PATH=/bigdisk/build-system/arena/20150507/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/20150507/gcc-head/install-s390x-default/bin/../libexec/gcc/s390x-ibm-linux-gnu/6.0.0/lto-wrapper Target: s390x-ibm-linux-gnu Configured with: /bigdisk/build-system/arena/20150507/gcc-head/src/configure --enable-shared --with-system-zlib --enable-threads=posix --enable-__cxa_atexit --enable-checking --with-diagnostics-color=never --prefix=/bigdisk/build-system/arena/20150507/gcc-head/install-s390x-default --enable-languages=c,c++,objc,obj-c++,fortran,java,ada,go --with-mode=zarch Thread model: posix gcc version 6.0.0 20150507 (experimental) (GCC)
reply other threads:[~2015-05-08 11:03 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=201505081103.t48B326m032728@d06av09.portsmouth.uk.ibm.com \ --to=krebbel@linux.vnet.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: linkBe 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).