public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error
@ 2016-05-25 18:48 sergiodj+buildbot
  2016-05-25 18:50 ` Failures on AIX-POWER7-plain, branch gdb-7.11-branch sergiodj+buildbot
                   ` (13 more replies)
  0 siblings, 14 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 136613ef0c6850427317e57be1b644080ff6decb ***

Author: Pedro Alves <palves@redhat.com>
Branch: gdb-7.11-branch
Commit: 136613ef0c6850427317e57be1b644080ff6decb

Fix PR gdb/19828: gdb -p <process from a container>: internal error

When GDB attaches to a process, it looks at the /proc/PID/task/ dir
for all clone threads of that process, and attaches to each of them.

Usually, if there is more than one clone thread, it means the program
is multi threaded and linked with pthreads.  Thus when GDB soon after
attaching finds and loads a libthread_db matching the process, it'll
add a thread to the thread list for each of the initially found
lower-level LWPs.

If, however, GDB fails to find/load a matching libthread_db, nothing
is adding the LWPs to the thread list.  And because of that, "detach"
hits an internal error:

  (gdb) PASS: gdb.threads/clone-attach-detach.exp: fg attach 1: attach
  info threads
    Id   Target Id         Frame
  * 1    LWP 6891 "clone-attach-de" 0x00007f87e5fd0790 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:84
  (gdb) FAIL: gdb.threads/clone-attach-detach.exp: fg attach 1: info threads shows two LWPs
  detach
  .../src/gdb/thread.c:1010: internal-error: is_executing: Assertion `tp' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)
  FAIL: gdb.threads/clone-attach-detach.exp: fg attach 1: detach (GDB internal error)

>From here:

  ...
  #8  0x00000000007ba7cc in internal_error (file=0x98ea68 ".../src/gdb/thread.c", line=1010, fmt=0x98ea30 "%s: Assertion `%s' failed.")
      at .../src/gdb/common/errors.c:55
  #9  0x000000000064bb83 in is_executing (ptid=...) at .../src/gdb/thread.c:1010
  #10 0x00000000004c23bb in get_pending_status (lp=0x12c5cc0, status=0x7fffffffdc0c) at .../src/gdb/linux-nat.c:1235
  #11 0x00000000004c2738 in detach_callback (lp=0x12c5cc0, data=0x0) at .../src/gdb/linux-nat.c:1317
  #12 0x00000000004c1a2a in iterate_over_lwps (filter=..., callback=0x4c2599 <detach_callback>, data=0x0) at .../src/gdb/linux-nat.c:899
  #13 0x00000000004c295c in linux_nat_detach (ops=0xe7bd30, args=0x0, from_tty=1) at .../src/gdb/linux-nat.c:1358
  #14 0x000000000068284d in delegate_detach (self=0xe7bd30, arg1=0x0, arg2=1) at .../src/gdb/target-delegates.c:34
  #15 0x0000000000694141 in target_detach (args=0x0, from_tty=1) at .../src/gdb/target.c:2241
  #16 0x0000000000630582 in detach_command (args=0x0, from_tty=1) at .../src/gdb/infcmd.c:2975
  ...

Tested on x86-64 Fedora 23.  Also confirmed the test passes against
gdbserver with "maint set target-non-stop".

Unfortunately, making GDB add LWPs to the thread list sooner exposes
inefficiencies that in turn result in
gdb.threads/attach-many-short-lived-threads.exp timing out frequently.
Since that testcase is really a contrived use case designed to stress
some aspects of attach/detach and thread listing, not really
representative of real programs, this commit disables the test.

gdb/ChangeLog:
2016-05-25  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-nat.c (attach_proc_task_lwp_callback): Mark the lwp
	resumed, and add the thread to GDB's thread list.

testsuite/ChangeLog:
2016-05-25  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* gdb.threads/clone-attach-detach.c: New file.
	* gdb.threads/clone-attach-detach.exp: New file.
	* gdb.threads/attach-many-short-lived-threads.exp: Skip.


^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on AIX-POWER7-plain, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
@ 2016-05-25 18:50 ` sergiodj+buildbot
  2016-05-25 19:10 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
                   ` (12 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 18:50 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	aix-power7-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/AIX-POWER7-plain/builds/2384>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/AIX-POWER7-plain/.git/tree/?h=gdb-7.11-branch&id=5a8ed7b7a88c9406d5694880f3bda0f42a49dd93>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/next-while-other-thread-longjmps.exp: next to line 1
PASS -> FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock off: b end
PASS -> FAIL: gdb.threads/tls.exp: continue to third thread
PASS -> FAIL: gdb.threads/tls.exp: third thread print me
PASS -> FAIL: gdb.threads/tls.exp: continue to synch point
PASS -> FAIL: gdb.threads/tls.exp: threads exited
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
  2016-05-25 18:50 ` Failures on AIX-POWER7-plain, branch gdb-7.11-branch sergiodj+buildbot
@ 2016-05-25 19:10 ` sergiodj+buildbot
  2016-05-25 19:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
                   ` (11 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 19:10 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

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

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-native-gdbserver-m64/.git/tree/?h=gdb-7.11-branch&id=5a83d9e4b0b3558d2b651c8a6d62dec22e07d702>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.trace/collection.exp: collect a[b]: start trace experiment
PASS -> FAIL: gdb.trace/collection.exp: collect a[b]: run trace experiment
PASS -> FAIL: gdb.trace/collection.exp: collect a[b]: tfind test frame
PASS -> FAIL: gdb.trace/collection.exp: collect a[b]: got expected value '3'
PASS -> FAIL: gdb.trace/collection.exp: collect a[b]: cease trace debugging
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
  2016-05-25 18:50 ` Failures on AIX-POWER7-plain, branch gdb-7.11-branch sergiodj+buildbot
  2016-05-25 19:10 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
@ 2016-05-25 19:11 ` sergiodj+buildbot
  2016-05-25 19:18 ` Failures on Fedora-i686, " sergiodj+buildbot
                   ` (10 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 19:11 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-gdbserver-m32/builds/3645>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-native-gdbserver-m32/.git/tree/?h=gdb-7.11-branch&id=ab31cfef0309d88ee1a917af042c59530660ac8c>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
new FAIL: gdb.base/interrupt.exp: echo data
new FAIL: gdb.base/interrupt.exp: Send Control-C, second time
new FAIL: gdb.base/interrupt.exp: signal SIGINT
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-i686, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (2 preceding siblings ...)
  2016-05-25 19:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
@ 2016-05-25 19:18 ` sergiodj+buildbot
  2016-05-25 19:23 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
                   ` (9 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 19:18 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/3658>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-i686/.git/tree/?h=gdb-7.11-branch&id=5cef4d8eef32a64be1578bbc6afaad72206d4270>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (4 preceding siblings ...)
  2016-05-25 19:23 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
@ 2016-05-25 19:23 ` sergiodj+buildbot
  2016-05-25 20:44 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
                   ` (7 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 19:23 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-extended-gdbserver-m32/builds/3643>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-native-extended-gdbserver-m32/.git/tree/?h=gdb-7.11-branch&id=dc985d364dc7509d17bc895602eb56d41bee2eab>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (3 preceding siblings ...)
  2016-05-25 19:18 ` Failures on Fedora-i686, " sergiodj+buildbot
@ 2016-05-25 19:23 ` sergiodj+buildbot
  2016-05-25 19:23 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
                   ` (8 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 19:23 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3649>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=cea25a4e20da0f999176d2f07f04ed77157cc21f>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Debian-i686-native-extended-gdbserver, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (5 preceding siblings ...)
  2016-05-25 19:23 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
@ 2016-05-25 20:44 ` sergiodj+buildbot
  2016-05-25 20:54 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
                   ` (6 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 20:44 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	wildebeest-debian-wheezy-i686

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

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Debian-i686-native-extended-gdbserver/.git/tree/?h=gdb-7.11-branch&id=8d8e804c7da8b7d770ca965760e5e6765b6610e8>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/forking-threads-plus-breakpoint.exp: cond_bp_target=1: detach_on_fork=on: displaced=off: inferior 1 exited
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-s390x-m64, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (6 preceding siblings ...)
  2016-05-25 20:44 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
@ 2016-05-25 20:54 ` sergiodj+buildbot
  2016-05-25 21:01 ` Failures on Debian-i686, " sergiodj+buildbot
                   ` (5 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 20:54 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	marist-fedora-s390x

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-s390x-m64/builds/3217>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-s390x-m64/.git/tree/?h=gdb-7.11-branch&id=50e2c37dcc26cbfdca408a6a6e1e0285d434a5d9>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.reverse/s390-mvcle.exp: reverse to marker1
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Debian-i686, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (7 preceding siblings ...)
  2016-05-25 20:54 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
@ 2016-05-25 21:01 ` sergiodj+buildbot
  2016-05-26  0:18 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
                   ` (4 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 21:01 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	wildebeest-debian-wheezy-i686

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Debian-i686/builds/3558>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Debian-i686/.git/tree/?h=gdb-7.11-branch&id=86b4a7e5ad59cd27eab93ca126b36cfeb404df0d>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.base/longjmp.exp: next over patt3
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Debian-s390x-native-extended-gdbserver-m64, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (8 preceding siblings ...)
  2016-05-25 21:01 ` Failures on Debian-i686, " sergiodj+buildbot
@ 2016-05-26  0:18 ` sergiodj+buildbot
  2016-05-26 17:08 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
                   ` (3 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-26  0:18 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	debian-wheezy-s390x-1

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

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

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

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (9 preceding siblings ...)
  2016-05-26  0:18 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
@ 2016-05-26 17:08 ` sergiodj+buildbot
  2016-05-26 17:12 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
                   ` (2 subsequent siblings)
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-26 17:08 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-ppc64be-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-ppc64be-cc-with-index/builds/3591>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-ppc64be-cc-with-index/.git/tree/?h=gdb-7.11-branch&id=dac330a8e6cbb73296b578ec3333fad361026e94>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.base/checkpoint-ns.exp: breakpoint 1 5 one
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-ppc64be-native-extended-gdbserver-m64, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (10 preceding siblings ...)
  2016-05-26 17:08 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
@ 2016-05-26 17:12 ` sergiodj+buildbot
  2016-05-26 23:32 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
  2016-05-27  0:21 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-26 17:12 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-ppc64be-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-ppc64be-native-extended-gdbserver-m64/builds/3596>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-ppc64be-native-extended-gdbserver-m64/.git/tree/?h=gdb-7.11-branch&id=37cbb5089ed8d455f2e47fe83d56471b901377b0>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
PASS -> FAIL: gdb.threads/thread-unwindonsignal.exp: continue until exit
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-ppc64le-native-extended-gdbserver-m64, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (11 preceding siblings ...)
  2016-05-26 17:12 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
@ 2016-05-26 23:32 ` sergiodj+buildbot
  2016-05-27  0:21 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-26 23:32 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-ppc64le-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-ppc64le-native-extended-gdbserver-m64/builds/3531>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-ppc64le-native-extended-gdbserver-m64/.git/tree/?h=gdb-7.11-branch&id=9a47f92c3e54bd217ca3c0c8d898d70543aa3796>

*** Internal error on buildslave (no space left on device). ***
*** Please report this to the buildslave owner (see <http://gdb-build.sergiodj.net//buildslaves/fedora-ppc64le-1>) ***

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.base/checkpoint.exp: break1 four
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-ppc64le-native-gdbserver-m64, branch gdb-7.11-branch
  2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
                   ` (12 preceding siblings ...)
  2016-05-26 23:32 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
@ 2016-05-27  0:21 ` sergiodj+buildbot
  13 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-27  0:21 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-ppc64le-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-ppc64le-native-gdbserver-m64/builds/3517>

Commit(s) tested:
	136613ef0c6850427317e57be1b644080ff6decb

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR gdb/19828: gdb -p <process from a container>: internal error

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-ppc64le-native-gdbserver-m64/.git/tree/?h=gdb-7.11-branch&id=19a13b4116fb5d8aed1de8c3b53b6ce344620806>

*** Diff to previous build ***
============================
new FAIL: gdb.base/commands.exp: continue with watch
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-06-01  1:18 [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.11.1.DATE-git sergiodj+buildbot
@ 2016-06-01  1:38 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  1:38 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3684>

Commit(s) tested:
	d03dfbf66983602a4cdb97c37edd54c420ceed40

Author(s) (in the same order as the commits):
	Joel Brobecker <brobecker@adacore.com>

Subject:
	Bump GDB version number to 7.11.1.DATE-git.

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=cac463b2c23566504cfa1b584781b2d818503676>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-06-01  0:54 [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.11.1 sergiodj+buildbot
@ 2016-06-01  1:07 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  1:07 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3683>

Commit(s) tested:
	41d82368c333de4f7ec3fd7734ee683055e8c35c

Author(s) (in the same order as the commits):
	Joel Brobecker <brobecker@adacore.com>

Subject:
	Set GDB version number to 7.11.1.

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=8c209d88f1b82bfb76f0f3a7e291411ced337830>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: force loop break in thread 2
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: stepped thread under control
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-05-25 17:52 [binutils-gdb/gdb-7.11-branch] Make gdb/linux-nat.c consider a waitstatus pending on the infrun side sergiodj+buildbot
@ 2016-05-25 18:55 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 18:55 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3648>

Commit(s) tested:
	a0de87e7be6a58dfeb9bfb00172dbd975dabb72e

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Make gdb/linux-nat.c consider a waitstatus pending on the infrun side

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=e9b99efbf4a2b5cea38f04142802f78a79c1eb4f>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork one
PASS -> FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork two
PASS -> FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork three
PASS -> FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork four
PASS -> FAIL: gdb.base/checkpoint.exp: Exit, dropped into next fork five
PASS -> FAIL: gdb.base/checkpoint.exp: info checkpoints two
PASS -> FAIL: gdb.base/checkpoint.exp: kill all one
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 0
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 1
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 2
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 3
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 4
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 5
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 6
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 7
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 8
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 9
PASS -> FAIL: gdb.base/checkpoint.exp: no more checkpoint 10
PASS -> FAIL: gdb.base/checkpoint-ns.exp: Exit, dropped into next fork one
PASS -> FAIL: gdb.base/checkpoint-ns.exp: Exit, dropped into next fork two
PASS -> FAIL: gdb.base/checkpoint-ns.exp: Exit, dropped into next fork three
PASS -> FAIL: gdb.base/checkpoint-ns.exp: Exit, dropped into next fork four
PASS -> FAIL: gdb.base/checkpoint-ns.exp: Exit, dropped into next fork five
PASS -> FAIL: gdb.base/checkpoint-ns.exp: info checkpoints two
PASS -> FAIL: gdb.base/checkpoint-ns.exp: kill all one
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 0
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 1
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 2
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 3
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 4
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 5
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 6
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 7
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 8
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 9
PASS -> FAIL: gdb.base/checkpoint-ns.exp: no more checkpoint 10
new FAIL: gdb.cp/no-dmgl-verbose.exp: setting breakpoint at 'f
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-05-18 14:59 [binutils-gdb/gdb-7.11-branch] Add mi-threads-interrupt.exp test (PR 20039) sergiodj+buildbot
@ 2016-05-18 15:53 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 15:53 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3597>

Commit(s) tested:
	cf2cd51217c0b99f5370708cc3932c12a1f4edad

Author(s) (in the same order as the commits):
	Simon Marchi <simon.marchi@ericsson.com>

Subject:
	Add mi-threads-interrupt.exp test (PR 20039)

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=3f547b9dede4726b243a3d60fbd7bce01c5cb82f>

*** Regressions found ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: continue to sigusr1_handler
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: continue to sigusr1_handler
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-05-18 14:48 [binutils-gdb/gdb-7.11-branch] Fix double prompt output after run control MI commands with mi-async on (PR 20045) sergiodj+buildbot
@ 2016-05-18 15:27 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 15:27 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3596>

Commit(s) tested:
	f0a8d0dc70eddbf1e323e8c07f5092ff5e327548

Author(s) (in the same order as the commits):
	Simon Marchi <simon.marchi@ericsson.com>

Subject:
	Fix double prompt output after run control MI commands with mi-async on (PR 20045)

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=4efa4130ca78db98cf85eaf400373f056d5d961a>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-05-17 22:13 [binutils-gdb/gdb-7.11-branch] Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077) sergiodj+buildbot
@ 2016-05-18  1:33 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-18  1:33 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-4

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3590>

Commit(s) tested:
	b5f0db46b3057bcb64243e7da0943717abd6459b

Author(s) (in the same order as the commits):
	Simon Marchi <simon.marchi@ericsson.com>

Subject:
	Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077)

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=aade713d509c368e5230257a7aeee07b46c7d09d>

*** Regressions found ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: continue to sigusr1_handler
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: continue to sigusr1_handler
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-05-16 21:17 [binutils-gdb/gdb-7.11-branch] Use target_terminal_ours_for_output in MI sergiodj+buildbot
@ 2016-05-16 21:19 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-16 21:19 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3577>

Commit(s) tested:
	7f8e34d8604098e221f342cf162898fb25499900

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Use target_terminal_ours_for_output in MI

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=406058645676b0016f0282104ac8ac773b890b30>

*** Regressions found ***
============================
PASS -> FAIL: gdb.base/annota1.exp: signal sent
PASS -> FAIL: gdb.base/annota3.exp: signal sent
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/annota1.exp: signal sent
PASS -> FAIL: gdb.base/annota3.exp: signal sent
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-05-03 11:55 [binutils-gdb/gdb-7.11-branch] Fix gdb/python/python.c use-after-free sergiodj+buildbot
@ 2016-05-03 13:38 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 13:38 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3529>

Commit(s) tested:
	329dec6fc5f2efa83d626583135081b53abe8729

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix gdb/python/python.c use-after-free

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=c461ab45e9d8ed152f353b120eee9838af7ef9bd>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: continue to sigusr1_handler
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: continue to sigusr1_handler
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-05-03 11:46 [binutils-gdb/gdb-7.11-branch] Remove gdb/python/python.c code that handles strlen failing with -1 sergiodj+buildbot
@ 2016-05-03 13:08 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 13:08 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3528>

Commit(s) tested:
	aaa3178dfb979f8ec476a326aca273125a1e3ee9

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Remove gdb/python/python.c code that handles strlen failing with -1

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=6c2794f8747d14ee585866d57ce85fd77b08bad9>

*** Regressions found ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-04-27 19:52 [binutils-gdb/gdb-7.11-branch] Workaround gdbserver<7.7 for setfs sergiodj+buildbot
@ 2016-04-27 20:09 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 20:09 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3501>

Commit(s) tested:
	a6ff23076f49c6322d96a76e0098f8019139bc4e

Author(s) (in the same order as the commits):
	Jan Kratochvil <jan.kratochvil@redhat.com>

Subject:
	Workaround gdbserver<7.7 for setfs

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=cf998d050cf93e12b044d9884a1799b9ac45df4f>

*** Regressions found ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-04-16  0:19 [binutils-gdb/gdb-7.11-branch] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT sergiodj+buildbot
@ 2016-04-16  0:26 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-04-16  0:26 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3421>

Commit(s) tested:
	da611eed9a74de742e9436b6fdd92041b6e9bbf1

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=e8d54b4a84f4c78b974f6ccf88de6dba05b4cf7e>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 2
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-04-15 23:43 [binutils-gdb/gdb-7.11-branch] Handle MIPS Linux SIGTRAP siginfo.si_code values sergiodj+buildbot
@ 2016-04-15 23:47 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-04-15 23:47 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3420>

Commit(s) tested:
	619f36aa006c4263ec17b1d2a73613f840042c16

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Handle MIPS Linux SIGTRAP siginfo.si_code values

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=67945e3c5170eaeb5d11fca0d30f0437f8109698>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: continue to sigusr1_handler
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr2: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: continue to sigusr1_handler
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-04-13 13:51 [binutils-gdb/gdb-7.11-branch] Fix PR remote/19840: gdb crashes on reverse-stepi sergiodj+buildbot
@ 2016-04-13 14:08 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 14:08 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3403>

Commit(s) tested:
	6b9ef0d488c556339aea7b095ef7a9b6bf6b1af1

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Fix PR remote/19840: gdb crashes on reverse-stepi

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=f9ad16b129fdf87fe75688a632d11e1d209d5336>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 3
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: continue: continue
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 3
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-03-31 19:43 [binutils-gdb/gdb-7.11-branch] Add regression test for PR gdb/19858 (JIT code registration on attach) sergiodj+buildbot
@ 2016-04-01  0:14 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-04-01  0:14 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3316>

Commit(s) tested:
	85af34ee0211eedf8d30a5c44dfc59dddf8b512a

Author(s) (in the same order as the commits):
	Pedro Alves <palves@redhat.com>

Subject:
	Add regression test for PR gdb/19858 (JIT code registration on attach)

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=28a9fc16bf8ceb19720bdfd5af01674c38cb6f7c>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-03-31 19:23 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach sergiodj+buildbot
@ 2016-03-31 23:18 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 23:18 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3314>

Commit(s) tested:
	cd64cabb8c66a5565fc33bf66a07c08bc767e413

Author(s) (in the same order as the commits):
	Yichao Yu <yyc1992@gmail.com>

Subject:
	Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=a5fc353b6c7dbbb3baa58fbd56ceba2ba0e74477>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: next
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-03-17 11:28 [binutils-gdb/gdb-7.11-branch] btrace: fix PR gdb/19829 sergiodj+buildbot
@ 2016-03-18  0:13 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-03-18  0:13 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3236>

Commit(s) tested:
	2ef34d11f61d79dcb152713aa059051d8cd3295d

Author(s) (in the same order as the commits):
	Markus Metzger <markus.t.metzger@intel.com>

Subject:
	btrace: fix PR gdb/19829

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=d09e63f92a8883d96e8fb78eace21a760997468f>

*** Regressions found ***
============================
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/interrupt.exp: continue
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-22 16:28 [binutils-gdb/gdb-7.11-branch] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print' sergiodj+buildbot
@ 2016-02-22 16:31 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 16:31 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-4

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3069>

Commit(s) tested:
	3d58f8997229b9045899dd306a47a3c27d03a9fd

Author(s) (in the same order as the commits):
	Jan Kratochvil <jan.kratochvil@redhat.com>

Subject:
	gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=f37742b8666b2424965362edb826994842e0290b>

*** Regressions found ***
============================
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-16 17:31 [binutils-gdb/gdb-7.11-branch] PR remote/19496, internal err forking-threads-plus-bkpt sergiodj+buildbot
@ 2016-02-16 17:34 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 17:34 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3048>

Commit(s) tested:
	e993d610a980ea8df9200f158bfae69308c2138d

Author(s) (in the same order as the commits):
	Don Breazeal <donb@codesourcery.com>

Subject:
	PR remote/19496, internal err forking-threads-plus-bkpt

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=e895258ff9cdb6be90e558d5c7988c6e655de719>

*** Regressions found ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-15 18:07 [binutils-gdb/gdb-7.11-branch] Fix more testcases with standard_output_file sergiodj+buildbot
@ 2016-02-15 18:09 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 18:09 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-3

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3036>

Commit(s) tested:
	8b6bd5aca63189590498195a7a2696cde021c9cd

Author(s) (in the same order as the commits):
	Jan Kratochvil <jan.kratochvil@redhat.com>

Subject:
	Fix more testcases with standard_output_file.

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=e97028d2ff77c7e05942737f65827e0243727167>

*** Regressions found ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-15 16:29 [binutils-gdb/gdb-7.11-branch] i386-biarch-core.exp: Use standard_output_file sergiodj+buildbot
@ 2016-02-15 16:31 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 16:31 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3034>

Commit(s) tested:
	2d059a33d890c017c8105b102a6b56ccbd6128b2

Author(s) (in the same order as the commits):
	Simon Marchi <simon.marchi@ericsson.com>

Subject:
	i386-biarch-core.exp: Use standard_output_file

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=4d81fe99515bac2943c21df4b838a0ad823450f9>

*** Regressions found ***
============================
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-10 16:55 [binutils-gdb/gdb-7.11-branch] Clear *VAL in regcache_raw_read_unsigned sergiodj+buildbot
@ 2016-02-10 16:56 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 16:56 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-4

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3004>

Commit(s) tested:
	83d9e733abe9cc0553f899064a955a6255550ade

Author(s) (in the same order as the commits):
	Yao Qi <yao.qi@linaro.org>

Subject:
	Clear *VAL in regcache_raw_read_unsigned

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=c8df1a8b2555b9440e1d1add67c6321f63f9566e>

*** Regressions found ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
new FAIL: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
new FAIL: gdb.fortran/vla-sizeof.exp: print sizeof non-associated pvla
new FAIL: gdb.fortran/vla-value.exp: print undefined pvla
new FAIL: gdb.fortran/vla-value.exp: print non-associated &pvla
new FAIL: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)
new FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was filled (passed fixed array)
new FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was mofified in debugger (passed fixed array)
new FAIL: gdb.fortran/vla-value-sub-finish.exp: print array2 in foo after it was filled
new FAIL: gdb.fortran/vla-value-sub-finish.exp: print array2 in foo after it was mofified in debugger
new FAIL: gdb.fortran/vla-value-sub-finish.exp: finish function
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/win_fu_syms.exp: compilation foo.adb
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
new FAIL: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
new FAIL: gdb.fortran/vla-sizeof.exp: print sizeof non-associated pvla
new FAIL: gdb.fortran/vla-value.exp: print undefined pvla
new FAIL: gdb.fortran/vla-value.exp: print non-associated &pvla
new FAIL: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)
PASS -> FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was filled (passed fixed array)
PASS -> FAIL: gdb.fortran/vla-value-sub.exp: print array2 in foo after it was mofified in debugger (passed fixed array)
PASS -> FAIL: gdb.fortran/vla-value-sub-finish.exp: print array2 in foo after it was filled
PASS -> FAIL: gdb.fortran/vla-value-sub-finish.exp: print array2 in foo after it was mofified in debugger
PASS -> FAIL: gdb.fortran/vla-value-sub-finish.exp: finish function
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-10  9:41 [binutils-gdb/gdb-7.11-branch] gdb/version.in: Replace -cvs suffix by -git suffix sergiodj+buildbot
@ 2016-02-10  9:41 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  9:41 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/2996>

Commit(s) tested:
	7bcc056ca977328fa96a24fd747834f100be863a

Author(s) (in the same order as the commits):
	Joel Brobecker <brobecker@adacore.com>

Subject:
	gdb/version.in: Replace -cvs suffix by -git suffix

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=18b2233168c912a3f5875d4da39e3ec162b02e1d>

*** Regressions found ***
============================
new FAIL: gdb.base/annota1.exp: signal sent (timeout)
new FAIL: gdb.base/annota3.exp: signal sent (pattern 4) (timeout)
============================


*** Regressions against the baseline ***
============================
new FAIL: gdb.ada/fun_renaming.exp: print n(1)
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/annota1.exp: signal sent (timeout)
new FAIL: gdb.base/annota3.exp: signal sent (pattern 4) (timeout)
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-10  4:32 [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.10.90.DATE-cvs sergiodj+buildbot
@ 2016-02-10  6:07 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  6:07 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/2995>

Commit(s) tested:
	45e8913772c2db1235b3a0eb113d804cb254af13

Author(s) (in the same order as the commits):
	Joel Brobecker <brobecker@adacore.com>

Subject:
	Bump GDB version number to 7.10.90.DATE-cvs.

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=917fc363326ad8b30735a2364842d16b79049ada>

*** Regressions found ***
============================
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================


*** Regressions against the baseline ***
============================
new FAIL: gdb.ada/fun_renaming.exp: print n(1)
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-10  4:15 [binutils-gdb/gdb-7.11-branch] gdb/NEWS: Change "since GDB 7.10" -> "in GDB 7.11" sergiodj+buildbot
@ 2016-02-10  5:18 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  5:18 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/2993>

Commit(s) tested:
	4fd877f0a54fbdfc28680aa24f3133f14648ee10

Author(s) (in the same order as the commits):
	Joel Brobecker <brobecker@adacore.com>

Subject:
	gdb/NEWS: Change "since GDB 7.10" -> "in GDB 7.11".

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=c88a9ccf16b9a66ee4f81b686cbedc98c5fbd75a>

*** Regressions found ***
============================
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================


*** Regressions against the baseline ***
============================
new FAIL: gdb.ada/fun_renaming.exp: print n(1)
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

* Failures on Fedora-x86_64-m32, branch gdb-7.11-branch
  2016-02-10  3:41 [binutils-gdb/gdb-7.11-branch] Bump version to 7.10.90.DATE-git sergiodj+buildbot
@ 2016-02-10  3:43 ` sergiodj+buildbot
  0 siblings, 0 replies; 40+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  3:43 UTC (permalink / raw)
  To: gdb-testers

Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/2989>

Commit(s) tested:
	d5d168eef1464c735c5dba0cf76d638bd27970b9

Author(s) (in the same order as the commits):
	Joel Brobecker <brobecker@adacore.com>

Subject:
	Bump version to 7.10.90.DATE-git.

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-m32/.git/tree/?h=gdb-7.11-branch&id=6ad30e38c3fc9db38fb81e5762ef242b8b147363>

*** Regressions found ***
============================
new FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step (pattern 3)
============================


*** Regressions against the baseline ***
============================
new FAIL: gdb.ada/fun_renaming.exp: print n(1)
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/interrupt.exp: continue (the program exited)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
new FAIL: gdb.python/py-unwind.exp: continue to breakpoint: break backtrace-broken
new FAIL: gdb.python/py-unwind.exp: Backtrace restored by unwinder (pattern 1)
new FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step (pattern 3)
============================




^ permalink raw reply	[flat|nested] 40+ messages in thread

end of thread, other threads:[~2016-06-01  1:32 UTC | newest]

Thread overview: 40+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-25 18:48 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
2016-05-25 18:50 ` Failures on AIX-POWER7-plain, branch gdb-7.11-branch sergiodj+buildbot
2016-05-25 19:10 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-05-25 19:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-05-25 19:18 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-05-25 19:23 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-05-25 19:23 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-05-25 20:44 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-05-25 20:54 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-05-25 21:01 ` Failures on Debian-i686, " sergiodj+buildbot
2016-05-26  0:18 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-26 17:08 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-05-26 17:12 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-26 23:32 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-05-27  0:21 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-06-01  1:18 [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.11.1.DATE-git sergiodj+buildbot
2016-06-01  1:38 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-06-01  0:54 [binutils-gdb/gdb-7.11-branch] Set GDB version number to 7.11.1 sergiodj+buildbot
2016-06-01  1:07 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-05-25 17:52 [binutils-gdb/gdb-7.11-branch] Make gdb/linux-nat.c consider a waitstatus pending on the infrun side sergiodj+buildbot
2016-05-25 18:55 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-05-18 14:59 [binutils-gdb/gdb-7.11-branch] Add mi-threads-interrupt.exp test (PR 20039) sergiodj+buildbot
2016-05-18 15:53 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-05-18 14:48 [binutils-gdb/gdb-7.11-branch] Fix double prompt output after run control MI commands with mi-async on (PR 20045) sergiodj+buildbot
2016-05-18 15:27 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-05-17 22:13 [binutils-gdb/gdb-7.11-branch] Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077) sergiodj+buildbot
2016-05-18  1:33 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-05-16 21:17 [binutils-gdb/gdb-7.11-branch] Use target_terminal_ours_for_output in MI sergiodj+buildbot
2016-05-16 21:19 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-05-03 11:55 [binutils-gdb/gdb-7.11-branch] Fix gdb/python/python.c use-after-free sergiodj+buildbot
2016-05-03 13:38 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-05-03 11:46 [binutils-gdb/gdb-7.11-branch] Remove gdb/python/python.c code that handles strlen failing with -1 sergiodj+buildbot
2016-05-03 13:08 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-04-27 19:52 [binutils-gdb/gdb-7.11-branch] Workaround gdbserver<7.7 for setfs sergiodj+buildbot
2016-04-27 20:09 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-04-16  0:19 [binutils-gdb/gdb-7.11-branch] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT sergiodj+buildbot
2016-04-16  0:26 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-04-15 23:43 [binutils-gdb/gdb-7.11-branch] Handle MIPS Linux SIGTRAP siginfo.si_code values sergiodj+buildbot
2016-04-15 23:47 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-04-13 13:51 [binutils-gdb/gdb-7.11-branch] Fix PR remote/19840: gdb crashes on reverse-stepi sergiodj+buildbot
2016-04-13 14:08 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-03-31 19:43 [binutils-gdb/gdb-7.11-branch] Add regression test for PR gdb/19858 (JIT code registration on attach) sergiodj+buildbot
2016-04-01  0:14 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-03-31 19:23 [binutils-gdb/gdb-7.11-branch] Fix PR gdb/19858: GDB doesn't register the JIT libraries on attach sergiodj+buildbot
2016-03-31 23:18 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-03-17 11:28 [binutils-gdb/gdb-7.11-branch] btrace: fix PR gdb/19829 sergiodj+buildbot
2016-03-18  0:13 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-22 16:28 [binutils-gdb/gdb-7.11-branch] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print' sergiodj+buildbot
2016-02-22 16:31 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-16 17:31 [binutils-gdb/gdb-7.11-branch] PR remote/19496, internal err forking-threads-plus-bkpt sergiodj+buildbot
2016-02-16 17:34 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-15 18:07 [binutils-gdb/gdb-7.11-branch] Fix more testcases with standard_output_file sergiodj+buildbot
2016-02-15 18:09 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-15 16:29 [binutils-gdb/gdb-7.11-branch] i386-biarch-core.exp: Use standard_output_file sergiodj+buildbot
2016-02-15 16:31 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10 16:55 [binutils-gdb/gdb-7.11-branch] Clear *VAL in regcache_raw_read_unsigned sergiodj+buildbot
2016-02-10 16:56 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  9:41 [binutils-gdb/gdb-7.11-branch] gdb/version.in: Replace -cvs suffix by -git suffix sergiodj+buildbot
2016-02-10  9:41 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  4:32 [binutils-gdb/gdb-7.11-branch] Bump GDB version number to 7.10.90.DATE-cvs sergiodj+buildbot
2016-02-10  6:07 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  4:15 [binutils-gdb/gdb-7.11-branch] gdb/NEWS: Change "since GDB 7.10" -> "in GDB 7.11" sergiodj+buildbot
2016-02-10  5:18 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot
2016-02-10  3:41 [binutils-gdb/gdb-7.11-branch] Bump version to 7.10.90.DATE-git sergiodj+buildbot
2016-02-10  3:43 ` Failures on Fedora-x86_64-m32, branch gdb-7.11-branch sergiodj+buildbot

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