This is the mail archive of the gdb-testers@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]

Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master


Buildslave:
	wildebeest-debian-wheezy-x86_64

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Debian-x86_64-native-extended-gdbserver-m64/builds/3599>

Commit(s) tested:
	e89c5eaa7208f06e927a79facff0316f4e550f6f

Author(s) (in the same order as the commits):
	H.J. Lu <hjl.tools@gmail.com>

Subject:
	Correct CpuMax in i386-opc.h

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Debian-x86_64-native-extended-gdbserver-m64/.git/tree/?h=master&id=a722062b4ffb5b45e8d594180c39f4557b3dcb4e>

*** Diff to previous build ***
============================
new FAIL: gdb.ada/mi_ex_cond.exp: Cannot run to main, testcase aborted
PASS -> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO: BINprelinkYESdebugSEPpieATTACH: attach-relinkYES: seen displacement message as NONZERO
PASS -> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugNO: BINprelinkYESdebugSEPpieATTACH: attach-relinkYES: attach main bt
PASS -> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkYESdebugNOpieATTACH: attach-relinkNO: seen displacement message as NONZERO
PASS -> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkYESdebugNOpieATTACH: attach-relinkNO: attach main bt
PASS -> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkYESdebugINpieATTACH: attach-relinkYES: seen displacement message as NONZERO
PASS -> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkYESdebugINpieATTACH: attach-relinkYES: attach main bt
PASS -> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkYESdebugINpieATTACH: attach-relinkNO: seen displacement message as NONZERO
PASS -> FAIL: gdb.base/break-interp.exp: LDprelinkNOdebugIN: BINprelinkYESdebugINpieATTACH: attach-relinkNO: attach main bt
PASS -> FAIL: gdb.base/interrupt.exp: Send Control-C, second time
PASS -> FAIL: gdb.base/interrupt.exp: signal SIGINT
PASS -> FAIL: gdb.base/paginate-after-ctrl-c-running.exp: ctrlc target running: got prompt
PASS -> FAIL: gdb.base/sigaltstack.exp: continue to catch
PASS -> FAIL: gdb.base/sigstep.exp: next to handler, si+advance in handler, next from handler: continue to signal
PASS -> FAIL: gdb.base/sigstep.exp: next to handler, nothing in handler, continue from handler: continue to signal
PASS -> FAIL: gdb.base/sigstep.exp: next to handler, nothing in handler, continue from handler: next to handler
PASS -> FAIL: gdb.base/sigstep.exp: step over handler: performing step
PASS -> FAIL: gdb.base/source-execution.exp: source source-execution.gdb
PASS -> FAIL: gdb.guile/guile.exp: source -s source2.scm
new FAIL: gdb.guile/scm-symtab.exp: Can't run to main
new FAIL: gdb.multi/multi-arch.exp: starting inferior 2
PASS -> FAIL: gdb.multi/multi-arch.exp: info inferiors
PASS -> FAIL: gdb.python/py-xmethods.exp: load the script file
PASS -> FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 5: attach
PASS -> FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 5: no new threads
PASS -> FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 5: set breakpoint always-inserted on
PASS -> FAIL: gdb.threads/continue-pending-status.exp: attempt 19: caught interrupt
PASS -> FAIL: gdb.threads/corethreads.exp: load core
============================


*** Complete list of XFAILs for this builder ***
============================
FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)
  - reported-by: GDB BuildBot Racy Detector (automatic)
  - number-of-racy-detections: 1 (in the last 30 days)
  - last-racyness-detected: 2016-05-17 22:43:59 UTC
FAIL: gdb.dwarf2/gdb-index.exp: touch binary
  - reported-by: GDB BuildBot Racy Detector (automatic)
  - number-of-racy-detections: 1 (in the last 30 days)
  - last-racyness-detected: 2016-05-17 22:43:59 UTC
FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=off: next over function call
  - reported-by: GDB BuildBot Racy Detector (automatic)
  - number-of-racy-detections: 1 (in the last 30 days)
  - last-racyness-detected: 2016-05-17 22:43:59 UTC
============================




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]