public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI
@ 2019-03-18 15:12 sergiodj+buildbot
2019-03-18 15:12 ` Failures on RHEL-s390x-m64, branch gdb-8.3-branch sergiodj+buildbot
` (11 more replies)
0 siblings, 12 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 15:12 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 6885905d1da17780b3f00f90e9b56340a7f239e8 ***
Author: Hannes Domani <ssbssa@yahoo.de>
Branch: gdb-8.3-branch
Commit: 6885905d1da17780b3f00f90e9b56340a7f239e8
Fix scrolling right in the TUI
This commit fixes two issues in scrolling right in the TUI:
#1 - Scrolling right with the arrow keys, the first keypress doesn't
do anything. The problem is that copy_source_line() checks if
(column < first_col), and because of the ++column directly before, it
basically starts with 1 instead of 0.
#2 - Scrolling right handles TABS and escaped characters as single
characters, which just looks weird. The problem is that there's a
spot that misses handling TABS.
gdb/ChangeLog:
2019-03-18 Hannes Domani <ssbssa@yahoo.de>
* tui/tui-source.c (copy_source_line): Fix handling of 'column'.
Handle tabs.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on RHEL-s390x-m64, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
@ 2019-03-18 15:12 ` sergiodj+buildbot
2019-03-18 19:43 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
` (10 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 15:12 UTC (permalink / raw)
To: gdb-testers
Buildslave:
rhel-7_1-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/RHEL-s390x-m64/builds/9516>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/RHEL-s390x-m64/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
new FAIL: gdb.python/python.exp: set the hook
PASS -> FAIL: gdb.python/python.exp: set the hook to default
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=1: inferior 1 exited
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=0: inferior 1 exited
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-extended-gdbserver-m64, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
2019-03-18 15:12 ` Failures on RHEL-s390x-m64, branch gdb-8.3-branch sergiodj+buildbot
@ 2019-03-18 19:43 ` sergiodj+buildbot
2019-03-18 20:19 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
` (9 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 19:43 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-extended-gdbserver-m64/builds/7819>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-extended-gdbserver-m64/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
FAIL -> UNRESOLVED: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=11: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=13: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=14: wait for stops
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
2019-03-18 15:12 ` Failures on RHEL-s390x-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-18 19:43 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
@ 2019-03-18 20:19 ` sergiodj+buildbot
2019-03-18 20:41 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
` (8 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 20:19 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7676>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=3: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=6: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-m64, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (2 preceding siblings ...)
2019-03-18 20:19 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
@ 2019-03-18 20:41 ` sergiodj+buildbot
2019-03-24 1:44 ` Failures on Fedora-i686, " sergiodj+buildbot
` (7 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 20:41 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-m64/builds/7634>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-m64/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
PASS -> UNRESOLVED: gdb.dwarf2/multidictionary.exp: GDB is alive
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.2: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.2: frame without args, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.2: select frame 1 again, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.2: select frame 1, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.3: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.3: frame without args, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.3: reset selection to thread 1.3
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.3: select frame 1, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_inferior: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_inferior: reset selection to thread 1.1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_inferior: select inferior again, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_inferior: select inferior, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_thread: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_thread: reset selection to thread 1.1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_thread: thread 1.2: select thread again, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_thread: thread 1.2: select thread, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_thread: thread 1.2: thread without args, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_thread: thread 1.3: select thread again, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_thread: thread 1.3: select thread, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_thread: thread 1.3: thread without args, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.2: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.2: frame without args, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.2: select frame 1 again, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.2: select frame 1, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.3: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.3: frame without args, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.3: reset selection to thread 1.3
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.3: select frame 1, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_inferior: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_inferior: reset selection to thread 1.1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_inferior: select inferior again, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_inferior: select inferior, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_thread: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_thread: reset selection to thread 1.1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_thread: thread 1.2: select thread again, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_thread: thread 1.2: select thread, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_thread: thread 1.2: thread without args, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_thread: thread 1.3: select thread again, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_thread: thread 1.3: select thread, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_thread: thread 1.3: thread without args, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.2: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.2: frame without args
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.2: select frame 1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.2: select frame 1 again
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.3: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.3: frame without args
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.3: reset selection to thread 1.3
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.3: select frame 1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_inferior: CLI select inferior
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_inferior: CLI select inferior again
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_inferior: reset selection to thread 1.1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_select_frame: thread 1.2: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_select_frame: thread 1.2: select frame 1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_select_frame: thread 1.2: select frame 1 again
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_select_frame: thread 1.3: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_select_frame: thread 1.3: reset selection to thread 1.3
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_select_frame: thread 1.3: select frame 1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_thread: reset selection to thread 1.1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_thread: thread 1.2: select thread
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_thread: thread 1.2: select thread again
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_thread: thread 1.2: thread without args
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_thread: thread 1.3: select thread
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_thread: thread 1.3: select thread again
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_thread: thread 1.3: thread without args
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_up_down: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_up_down: frame down
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_up_down: frame up
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_stack_select_frame: thread 1.2: -stack-select-frame again, event on MI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_stack_select_frame: thread 1.2: -stack-select-frame, event on MI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_stack_select_frame: thread 1.2: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_stack_select_frame: thread 1.3: -stack-select-frame, event on MI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_stack_select_frame: thread 1.3: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_stack_select_frame: thread 1.3: reset selection to thread 1.3
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_thread_select: flush CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_thread_select: reset selection to thread 1.1
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_thread_select: thread 1.2: -thread-select again, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_thread_select: thread 1.2: -thread-select, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_thread_select: thread 1.3: -thread-select again, event on CLI, ensure no output CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_thread_select: thread 1.3: -thread-select, event on CLI
UNRESOLVED -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_setup: inferior 2: set thread-specific breakpoint, thread 2.2
new FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_setup: inferior 2: thread 2.2 stops CLI
new FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_setup: inferior 2: thread 2.2 stops MI
PASS -> FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=0: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Fedora-i686, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (3 preceding siblings ...)
2019-03-18 20:41 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
@ 2019-03-24 1:44 ` sergiodj+buildbot
2019-03-24 1:51 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
` (6 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-24 1:44 UTC (permalink / raw)
To: gdb-testers
Buildslave:
fedora-x86-64-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/12333>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-i686/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=0: inferior 1 exited
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=1: inferior 1 exited
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Fedora-x86_64-cc-with-index, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (4 preceding siblings ...)
2019-03-24 1:44 ` Failures on Fedora-i686, " sergiodj+buildbot
@ 2019-03-24 1:51 ` sergiodj+buildbot
2019-03-24 2:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
` (5 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-24 1:51 UTC (permalink / raw)
To: gdb-testers
Buildslave:
fedora-x86-64-2
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cc-with-index/builds/12247>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-cc-with-index/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
new KFAIL: gdb.base/step-over-syscall.exp: clone: displaced=on: single step over clone
PASS -> KFAIL: gdb.threads/non-ldr-exit.exp: program exits normally
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (5 preceding siblings ...)
2019-03-24 1:51 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
@ 2019-03-24 2:46 ` sergiodj+buildbot
2019-03-24 2:50 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
` (4 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-24 2:46 UTC (permalink / raw)
To: gdb-testers
Buildslave:
fedora-x86-64-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-extended-gdbserver-m64/builds/12290>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-native-extended-gdbserver-m64/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
PASS -> UNRESOLVED: gdb.dwarf2/dw2-abs-hi-pc.exp: break hello
PASS -> FAIL: gdb.dwarf2/dw2-abs-hi-pc.exp: break world
PASS -> FAIL: gdb.reverse/step-precsave.exp: finish out of fn call
PASS -> FAIL: gdb.reverse/step-precsave.exp: next over call
PASS -> FAIL: gdb.reverse/step-precsave.exp: next test 1
PASS -> FAIL: gdb.reverse/step-precsave.exp: next test 2
PASS -> FAIL: gdb.reverse/step-precsave.exp: reload core file
PASS -> FAIL: gdb.reverse/step-precsave.exp: reverse step into fn call
PASS -> FAIL: gdb.reverse/step-precsave.exp: reverse stepi thru function return
PASS -> FAIL: gdb.reverse/step-precsave.exp: save process recfile
PASS -> FAIL: gdb.reverse/step-precsave.exp: set reverse execution
PASS -> FAIL: gdb.reverse/step-precsave.exp: simple stepi
PASS -> FAIL: gdb.reverse/step-precsave.exp: step into call
PASS -> FAIL: gdb.reverse/step-precsave.exp: step test 1
PASS -> FAIL: gdb.reverse/step-precsave.exp: step test 2
PASS -> FAIL: gdb.reverse/step-precsave.exp: step up to call
PASS -> FAIL: gdb.reverse/step-precsave.exp: stepi back from function call
PASS -> FAIL: gdb.reverse/step-precsave.exp: stepi into function call
PASS -> FAIL: gdb.reverse/step-precsave.exp: turn on process record
PASS -> UNRESOLVED: gdb.threads/attach-into-signal.exp: threaded: attach
new FAIL: gdb.threads/attach-into-signal.exp: threaded: thread apply 2 print $_siginfo.si_signo
PASS -> FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: no threads left
PASS -> FAIL: gdb.trace/mi-tsv-changed.exp: create delete modify: tvariable $tvar3 modified
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Fedora-x86_64-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (6 preceding siblings ...)
2019-03-24 2:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
@ 2019-03-24 2:50 ` sergiodj+buildbot
2019-03-24 3:14 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
` (3 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-24 2:50 UTC (permalink / raw)
To: gdb-testers
Buildslave:
fedora-x86-64-2
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-gdbserver-m64/builds/12253>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-native-gdbserver-m64/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=0: inferior 1 exited
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=1: inferior 1 exited
PASS -> FAIL: gdb.trace/mi-tsv-changed.exp: create delete modify: tvariable $tvar3 modified
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Fedora-x86_64-m64, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (7 preceding siblings ...)
2019-03-24 2:50 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
@ 2019-03-24 3:14 ` sergiodj+buildbot
2019-03-24 3:19 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
` (2 subsequent siblings)
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-24 3:14 UTC (permalink / raw)
To: gdb-testers
Buildslave:
fedora-x86-64-2
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m64/builds/12426>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-m64/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.base/step-over-syscall.exp: clone: displaced=off: single step over clone
PASS -> UNRESOLVED: gdb.mi/list-thread-groups-available.exp: list available thread groups
PASS -> UNRESOLVED: gdb.mi/list-thread-groups-available.exp: list available thread groups with filter
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Fedora-x86_64-m32, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (8 preceding siblings ...)
2019-03-24 3:14 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
@ 2019-03-24 3:19 ` sergiodj+buildbot
2019-03-26 3:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2019-03-26 14:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-24 3: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/12087>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-m32/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
new KFAIL: gdb.base/step-over-syscall.exp: clone: displaced=on: single step over clone
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (9 preceding siblings ...)
2019-03-24 3:19 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
@ 2019-03-26 3:51 ` sergiodj+buildbot
2019-03-26 14:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-26 3:51 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/12015>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-native-extended-gdbserver-m32/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-8.3-branch
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
` (10 preceding siblings ...)
2019-03-26 3:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
@ 2019-03-26 14:32 ` sergiodj+buildbot
11 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-26 14:32 UTC (permalink / raw)
To: gdb-testers
Buildslave:
fedora-x86-64-4
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-gdbserver-m32/builds/12024>
Commit(s) tested:
6885905d1da17780b3f00f90e9b56340a7f239e8
Author(s) (in the same order as the commits):
Hannes Domani <ssbssa@yahoo.de>
Subject:
Fix scrolling right in the TUI
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-native-gdbserver-m32/68/6885905d1da17780b3f00f90e9b56340a7f239e8/>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.ada/bp_enum_homonym.exp: run to pck.archive breakpoint
PASS -> FAIL: gdb.ada/bp_fun_addr.exp: run until breakpoint at bp_fun_addr'address
PASS -> FAIL: gdb.ada/bp_range_type.exp: print small_value
PASS -> FAIL: gdb.ada/bp_range_type.exp: run to breakpoint
PASS -> FAIL: gdb.ada/expr_delims.exp: continue
PASS -> FAIL: gdb.ada/expr_delims.exp: delete 1
PASS -> FAIL: gdb.ada/expr_delims.exp: print variable 'thread'
PASS -> FAIL: gdb.ada/mi_dyn_arr.exp: create bt varobj
PASS -> FAIL: gdb.ada/mi_dyn_arr.exp: list ggg1's children
PASS -> FAIL: gdb.ada/mi_dyn_arr.exp: mi runto main
PASS -> FAIL: gdb.ada/mi_dyn_arr.exp: run to foo.adb:22
new FAIL: gdb.ada/mi_dyn_arr.exp: wait for stop
PASS -> UNRESOLVED: gdb.ada/mi_exc_info.exp: -info-ada-exceptions
PASS -> FAIL: gdb.ada/mi_exc_info.exp: mi runto main
PASS -> FAIL: gdb.ada/mi_interface.exp: mi runto main
PASS -> FAIL: gdb.ada/mi_interface.exp: run to foo.adb:22
new FAIL: gdb.ada/mi_interface.exp: wait for stop
PASS -> FAIL: gdb.ada/mi_ref_changeable.exp: -var-update a at STOP_2
PASS -> FAIL: gdb.ada/mi_ref_changeable.exp: -var-update b at STOP_2
PASS -> FAIL: gdb.ada/mi_ref_changeable.exp: create varobj for a
PASS -> FAIL: gdb.ada/mi_ref_changeable.exp: create varobj for b
PASS -> FAIL: gdb.ada/mi_ref_changeable.exp: mi runto main
PASS -> FAIL: gdb.ada/mi_ref_changeable.exp: run to foo_rb20_056.adb:25
PASS -> FAIL: gdb.ada/mi_ref_changeable.exp: run to foo_rb20_056.adb:26
new FAIL: gdb.ada/mi_ref_changeable.exp: wait for stop
PASS -> FAIL: gdb.ada/mi_string_access.exp: Create var1 varobj
PASS -> FAIL: gdb.ada/mi_string_access.exp: Print var1
PASS -> FAIL: gdb.ada/mi_string_access.exp: Print var1 first child
PASS -> FAIL: gdb.ada/mi_string_access.exp: list var1's children
PASS -> FAIL: gdb.ada/mi_string_access.exp: mi runto main
PASS -> FAIL: gdb.ada/mi_string_access.exp: run to bar.adb:23
new FAIL: gdb.ada/mi_string_access.exp: wait for stop
PASS -> FAIL: gdb.ada/mi_task_arg.exp: -stack-list-arguments 1
PASS -> FAIL: gdb.ada/mi_task_arg.exp: mi runto task_switch.break_me
PASS -> FAIL: gdb.ada/mi_task_info.exp: -ada-task-info 3
PASS -> FAIL: gdb.ada/mi_task_info.exp: -ada-task-info with no argument
PASS -> FAIL: gdb.ada/mi_task_info.exp: mi runto task_switch.break_me
PASS -> FAIL: gdb.ada/mi_var_array.exp: create bt varobj
PASS -> FAIL: gdb.ada/mi_var_array.exp: list vta's children
PASS -> FAIL: gdb.ada/mi_var_array.exp: mi runto main
PASS -> FAIL: gdb.ada/mi_var_array.exp: run to bar.adb:28
new FAIL: gdb.ada/mi_var_array.exp: wait for stop
PASS -> FAIL: gdb.ada/mi_var_union.exp: Create var1 varobj
PASS -> FAIL: gdb.ada/mi_var_union.exp: list var1's children
PASS -> FAIL: gdb.ada/mi_var_union.exp: mi runto main
PASS -> FAIL: gdb.ada/mi_var_union.exp: run to bar.adb:28
new FAIL: gdb.ada/mi_var_union.exp: wait for stop
PASS -> FAIL: gdb.ada/out_of_line_in_inlined.exp: bt
PASS -> FAIL: gdb.ada/same_component_name.exp: run to top assign breakpoint
PASS -> FAIL: gdb.ada/task_bp.exp: run to dummy_task - from full symtab
PASS -> FAIL: gdb.ada/task_bp.exp: run to dummy_task - from psymtab
PASS -> FAIL: gdb.ada/task_bp.exp: run to pck.adb:dummy_task - from full symtab
PASS -> FAIL: gdb.ada/task_bp.exp: run to pck.adb:dummy_task - from psymtab
PASS -> FAIL: gdb.ada/task_bp.exp: run to pck.adb:pck.dummy_task - from full symtab
PASS -> FAIL: gdb.ada/task_bp.exp: run to pck.adb:pck.dummy_task - from psymtab
PASS -> FAIL: gdb.ada/task_bp.exp: run to pck.dummy_task - from full symtab
PASS -> FAIL: gdb.ada/task_bp.exp: run to pck.dummy_task - from psymtab
PASS -> FAIL: gdb.arch/i386-gnu-cfi.exp: backtrace
PASS -> FAIL: gdb.arch/i386-gnu-cfi.exp: continue to abort
PASS -> FAIL: gdb.arch/i386-gnu-cfi.exp: existence of the CFI inserted register
PASS -> FAIL: gdb.arch/i386-size-overlap.exp: backtrace shows the outer function
PASS -> FAIL: gdb.arch/i386-size-overlap.exp: run past main
PASS -> FAIL: gdb.arch/i386-size.exp: backtrace shows no function
PASS -> FAIL: gdb.arch/i386-size.exp: disassemble stops at end of main
PASS -> FAIL: gdb.arch/i386-size.exp: run past main
PASS -> FAIL: gdb.arch/i386-unwind.exp: backtrace past gdb1435
PASS -> FAIL: gdb.arch/i386-unwind.exp: run past gdb1435
PASS -> FAIL: gdb.base/a2-run.exp: run "a2-run" with no args
new FAIL: gdb.base/argv0-symlink.exp: argv[0] should be available on this target
new FAIL: gdb.base/argv0-symlink.exp: run to main
new FAIL: gdb.base/argv0-symlink.exp: set print elements 200
new FAIL: gdb.base/argv0-symlink.exp: set print elements unlimited
new FAIL: gdb.base/argv0-symlink.exp: set print repeats 200
new FAIL: gdb.base/argv0-symlink.exp: set print repeats unlimited
new FAIL: gdb.base/argv0-symlink.exp: show print elements
new FAIL: gdb.base/argv0-symlink.exp: show print repeats
PASS -> FAIL: gdb.base/break-fun-addr.exp: break-fun-addr1: p $pc == main
PASS -> FAIL: gdb.base/break-fun-addr.exp: break-fun-addr1: run to breakpoint at *main
PASS -> FAIL: gdb.base/break-fun-addr.exp: break-fun-addr2: p $pc == main
PASS -> UNRESOLVED: gdb.base/break-fun-addr.exp: break-fun-addr2: run to breakpoint at *main
PASS -> FAIL: gdb.base/break-inline.exp: break
PASS -> FAIL: gdb.base/break-probes.exp: call
PASS -> FAIL: gdb.base/break-probes.exp: run til our library loads
PASS -> FAIL: gdb.base/break.exp: Temporary breakpoint info
PASS -> FAIL: gdb.base/break.exp: backtrace from factorial
PASS -> FAIL: gdb.base/break.exp: break break.c:$l
PASS -> FAIL: gdb.base/break.exp: break lineno
PASS -> FAIL: gdb.base/break.exp: breakpoint offset +1
PASS -> FAIL: gdb.base/break.exp: continue to breakpoint at }
PASS -> FAIL: gdb.base/break.exp: continue to factorial
PASS -> FAIL: gdb.base/break.exp: continue until exit at recursive next test
PASS -> FAIL: gdb.base/break.exp: delete $bpnum
new FAIL: gdb.base/break.exp: info breakpoints
PASS -> FAIL: gdb.base/break.exp: list marker1
PASS -> UNRESOLVED: gdb.base/break.exp: next over recursive call
PASS -> FAIL: gdb.base/break.exp: next to recursive call
PASS -> FAIL: gdb.base/break.exp: rbreak junk
PASS -> FAIL: gdb.base/break.exp: run to factorial
PASS -> FAIL: gdb.base/break.exp: run until breakpoint set at a line number
PASS -> FAIL: gdb.base/break.exp: run until breakpoint set at small function, optimized file
PASS -> FAIL: gdb.base/break.exp: run until file:function
PASS -> FAIL: gdb.base/break.exp: run until file:linenum breakpoint
PASS -> FAIL: gdb.base/break.exp: run until function breakpoint
PASS -> FAIL: gdb.base/break.exp: run until function breakpoint, optimized file
PASS -> FAIL: gdb.base/break.exp: run until quoted breakpoint
PASS -> FAIL: gdb.base/break.exp: set $l = 47
PASS -> FAIL: gdb.base/break.exp: set convenience variable $foo to 81.5
PASS -> FAIL: gdb.base/break.exp: setting breakpoint at }
PASS -> FAIL: gdb.base/break.exp: step onto breakpoint
PASS -> UNRESOLVED: gdb.base/break.exp: temporary breakpoint function
PASS -> FAIL: gdb.base/break.exp: verify that they were cleared
PASS -> FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=exit: fork: break grandparent_done
PASS -> FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=exit: fork: continue
PASS -> FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=exit: fork: continue to grandchild fork
PASS -> FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=exit: fork: kill child
PASS -> FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=exit: fork: switch to parent
PASS -> FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=kill: fork: continue to grandchild fork
PASS -> FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=kill: fork: kill child
PASS -> FAIL: gdb.base/catch-fork-kill.exp: fork-kind=fork: exit-kind=kill: fork: switch to parent
PASS -> FAIL: gdb.base/catch-syscall.exp: execve: continue to main
PASS -> UNRESOLVED: gdb.base/catch-syscall.exp: execve: continue until exit
new FAIL: gdb.base/catch-syscall.exp: execve: info breakpoints
new FAIL: gdb.base/catch-syscall.exp: restarting inferior: entry/return:
PASS -> UNRESOLVED: gdb.base/catch-syscall.exp: restarting inferior: entry/return: continue until exit
new FAIL: gdb.base/catch-syscall.exp: restarting inferior: entry/return: info breakpoints
PASS -> FAIL: gdb.base/catch-syscall.exp: restarting inferior: entry/return: program has called chroot
PASS -> FAIL: gdb.base/catch-syscall.exp: restarting inferior: entry/return: syscall chroot has returned
PASS -> FAIL: gdb.base/charset.exp: check value of parsed character literal in ASCII
PASS -> FAIL: gdb.base/charset.exp: get integer valueof "sizeof
PASS -> FAIL: gdb.base/charset.exp: parse character literal in ASCII
PASS -> FAIL: gdb.base/charset.exp: parse string literal in ASCII
PASS -> FAIL: gdb.base/charset.exp: print string in ASCII
PASS -> FAIL: gdb.base/charset.exp: print the null character in ASCII
PASS -> FAIL: gdb.base/charset.exp: run until all strings have been initialized
PASS -> FAIL: gdb.base/charset.exp: set host-charset ASCII
PASS -> FAIL: gdb.base/charset.exp: set target-charset ASCII
PASS -> FAIL: gdb.base/chng-syms.exp: running to stop_here first time
PASS -> FAIL: gdb.base/chng-syms.exp: running with invalidated bpt condition after executable changes
PASS -> FAIL: gdb.base/commands.exp: bp_deleted_in_command_test: run factorial until breakpoint
PASS -> FAIL: gdb.base/commands.exp: error_clears_commands_left: cmd1 error
PASS -> FAIL: gdb.base/commands.exp: stray_arg0_test: #1
new FAIL: gdb.base/commands.exp: temporary_breakpoint_commands: begin commands in bp_deleted_in_command_test
PASS -> UNRESOLVED: gdb.base/commands.exp: temporary_breakpoint_commands: breakpoint
PASS -> FAIL: gdb.base/commands.exp: temporary_breakpoint_commands: run factorial until temporary breakpoint
new FAIL: gdb.base/condbreak.exp:
PASS -> FAIL: gdb.base/coredump-filter.exp: saving corefile for DoNotDump: p set_coredump_filter
PASS -> FAIL: gdb.base/coredump-filter.exp: saving corefile for DoNotDump: save corefile
PASS -> FAIL: gdb.base/coredump-filter.exp: saving corefile for non-Private-Anonymous: save corefile
PASS -> FAIL: gdb.base/coredump-filter.exp: saving corefile for non-Shared-Anonymous: p set_coredump_filter
PASS -> FAIL: gdb.base/coredump-filter.exp: saving corefile for non-Shared-Anonymous: save corefile
PASS -> FAIL: gdb.base/dbx.exp: file average.c:1
PASS -> FAIL: gdb.base/dbx.exp: func print_average
PASS -> FAIL: gdb.base/dbx.exp: func sum
PASS -> FAIL: gdb.base/dbx.exp: print first
PASS -> FAIL: gdb.base/dbx.exp: running to main
PASS -> FAIL: gdb.base/dbx.exp: stop in sum
PASS -> FAIL: gdb.base/dbx.exp: whereis my_list
PASS -> FAIL: gdb.base/dmsym.exp: continue
PASS -> FAIL: gdb.base/dmsym.exp: print val
PASS -> FAIL: gdb.base/dmsym.exp: run until breakpoint at BREAK
PASS -> FAIL: gdb.base/dprintf-pending.exp: run to resolved dprintf
PASS -> FAIL: gdb.base/dprintf-pending.exp: without symbols: run to resolved dprintf
PASS -> FAIL: gdb.base/dprintf.exp: 1st dprintf, gdb
PASS -> FAIL: gdb.base/dprintf.exp: 2nd dprintf, gdb
new FAIL: gdb.base/ena-dis-br.exp:
PASS -> FAIL: gdb.base/ena-dis-br.exp: break marker1
PASS -> UNRESOLVED: gdb.base/ena-dis-br.exp: break marker3
PASS -> FAIL: gdb.base/ena-dis-br.exp: continue to break marker1, 2nd time
PASS -> FAIL: gdb.base/ena-dis-br.exp: continue to ignored & auto-deleted break marker1
PASS -> FAIL: gdb.base/ena-dis-br.exp: continue until exit at no stop at auto-disabled break marker2
PASS -> FAIL: gdb.base/ena-dis-br.exp: disable break marker1
PASS -> FAIL: gdb.base/ena-dis-br.exp: enable del break marker1
new UNRESOLVED: gdb.base/ena-dis-br.exp: enable/disable break tests suppressed
PASS -> FAIL: gdb.base/ena-dis-br.exp: ignore break marker1
PASS -> FAIL: gdb.base/ena-dis-br.exp: info break marker1
new FAIL: gdb.base/ena-dis-br.exp: info breakpoints
PASS -> FAIL: gdb.base/ena-dis-br.exp: info ignored & disabled break marker1
PASS -> UNRESOLVED: gdb.base/ena-dis-br.exp: prepare to continue with ignore count
PASS -> FAIL: gdb.base/ending-run.exp: Cleared 2 by line
PASS -> FAIL: gdb.base/ending-run.exp: Step to return
PASS -> FAIL: gdb.base/ending-run.exp: all set to continue
PASS -> FAIL: gdb.base/ending-run.exp: b ending-run.c:1
PASS -> FAIL: gdb.base/ending-run.exp: b ending-run.c:11, two
PASS -> FAIL: gdb.base/ending-run.exp: clear worked
PASS -> FAIL: gdb.base/ending-run.exp: cleared bp at line before routine
PASS -> FAIL: gdb.base/ending-run.exp: cont
new FAIL: gdb.base/ending-run.exp: need to fix test for new compile outcome
PASS -> FAIL: gdb.base/ending-run.exp: run
PASS -> FAIL: gdb.base/ending-run.exp: step out of main
PASS -> FAIL: gdb.base/execl-update-breakpoints.exp: always-inserted off: continue across exec
PASS -> FAIL: gdb.base/execl-update-breakpoints.exp: always-inserted on: continue across exec
PASS -> FAIL: gdb.base/exitsignal.exp: $_exitcode is still void after restarting the inferior
PASS -> FAIL: gdb.base/exitsignal.exp: $_exitsignal is 11
new FAIL: gdb.base/exitsignal.exp:
PASS -> FAIL: gdb.base/find.exp: find string pattern
PASS -> FAIL: gdb.base/find.exp: pattern found at end of range
PASS -> FAIL: gdb.base/find.exp: pattern not found at end of range
PASS -> FAIL: gdb.base/find.exp: run until function breakpoint
new FAIL: gdb.base/find.exp: set *
new FAIL: gdb.base/foll-exec.exp:
PASS -> FAIL: gdb.base/foll-exec.exp: print execd-program/local_j
PASS -> FAIL: gdb.base/foll-fork.exp: follow child, detach off, command "continue": continue past fork
PASS -> FAIL: gdb.base/foll-fork.exp: follow child, detach off, command "continue": continue to breakpoint: continue unfollowed inferior to bp
PASS -> FAIL: gdb.base/foll-fork.exp: follow child, detach off, command "continue": inferior 1
PASS -> FAIL: gdb.base/foll-fork.exp: follow child, detach off, command "continue": info inferiors
PASS -> FAIL: gdb.base/foll-fork.exp: follow child, detach off, command "next 2": continue until exit at continue unfollowed inferior to end
PASS -> FAIL: gdb.base/foll-fork.exp: follow child, detach off, command "next 2": inferior 1
PASS -> FAIL: gdb.base/foll-fork.exp: follow child, detach off, command "next 2": info inferiors
PASS -> FAIL: gdb.base/foll-fork.exp: follow child, detach off, command "next 2": next 2 past fork
PASS -> FAIL: gdb.base/foll-fork.exp: follow parent, detach off, command "continue": continue past fork
PASS -> FAIL: gdb.base/foll-fork.exp: follow parent, detach off, command "continue": continue to breakpoint: continue unfollowed inferior to bp
PASS -> FAIL: gdb.base/foll-fork.exp: follow parent, detach off, command "continue": inferior 2
PASS -> FAIL: gdb.base/foll-fork.exp: follow parent, detach off, command "continue": info inferiors
PASS -> FAIL: gdb.base/foll-fork.exp: follow parent, detach off, command "next 2": continue until exit at continue unfollowed inferior to end
PASS -> FAIL: gdb.base/foll-fork.exp: follow parent, detach off, command "next 2": inferior 2
PASS -> FAIL: gdb.base/foll-fork.exp: follow parent, detach off, command "next 2": info inferiors
PASS -> FAIL: gdb.base/foll-fork.exp: follow parent, detach off, command "next 2": next 2 past fork
PASS -> FAIL: gdb.base/foll-vfork.exp: exec: vfork and exec child follow, to main bp: continue to bp
PASS -> FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: finish
PASS -> FAIL: gdb.base/foll-vfork.exp: exec: vfork relations in info inferiors: continue to bp
new FAIL: gdb.base/gdb-caching-proc.exp: argv[0] should be available on this target
PASS -> FAIL: gdb.base/gdb-caching-proc.exp: gdb_has_argv0 consistency
new FAIL: gdb.base/gdb-caching-proc.exp: run to main
new FAIL: gdb.base/gdb-caching-proc.exp: set print elements 200
new FAIL: gdb.base/gdb-caching-proc.exp: set print elements unlimited
new FAIL: gdb.base/gdb-caching-proc.exp: set print repeats 200
new FAIL: gdb.base/gdb-caching-proc.exp: set print repeats unlimited
new FAIL: gdb.base/gdb-caching-proc.exp: show print elements
new FAIL: gdb.base/gdb-caching-proc.exp: show print repeats
PASS -> UNRESOLVED: gdb.base/gdb-caching-proc.exp: skip_tsx_tests consistency
PASS -> FAIL: gdb.base/gnu-ifunc.exp: static: static gnu_ifunc
PASS -> FAIL: gdb.base/hbreak2.exp: continue to factorial
PASS -> FAIL: gdb.base/hbreak2.exp: hardware breakpoint insertion
PASS -> UNRESOLVED: gdb.base/hbreak2.exp: hardware breakpoint small function, optimized file
new FAIL: gdb.base/hbreak2.exp: info breakpoints
PASS -> FAIL: gdb.base/hbreak2.exp: run to factorial
PASS -> FAIL: gdb.base/hbreak2.exp: run until function breakpoint
PASS -> FAIL: gdb.base/hbreak2.exp: run until hardware function breakpoint, optimized file
PASS -> FAIL: gdb.base/infcall-exec.exp: call execlp
PASS -> FAIL: gdb.base/inferior-died.exp: continue to breakpoint: breakpoint
PASS -> FAIL: gdb.base/inferior-died.exp: inferior 2
PASS -> FAIL: gdb.base/inferior-died.exp: p 1
PASS -> FAIL: gdb.base/info-shared.exp: continue to breakpoint: library load #3
PASS -> FAIL: gdb.base/info-shared.exp: restart
PASS -> FAIL: gdb.base/jit-exec.exp: continue
new FAIL: gdb.base/label.exp:
PASS -> FAIL: gdb.base/label.exp: continue to 'there' after re-run
PASS -> FAIL: gdb.base/multi-forks.exp: detach 2
PASS -> FAIL: gdb.base/multi-forks.exp: detach 3
PASS -> FAIL: gdb.base/multi-forks.exp: detach 4
PASS -> FAIL: gdb.base/multi-forks.exp: detach 5
PASS -> FAIL: gdb.base/multi-forks.exp: did kill 6
PASS -> FAIL: gdb.base/multi-forks.exp: did kill 7
PASS -> FAIL: gdb.base/multi-forks.exp: did kill 8
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 1
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 10
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 11
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 12
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 14
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 2
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 3
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 4
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 5
PASS -> FAIL: gdb.base/multi-forks.exp: inferior 7
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 11
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 14
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 15
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 16
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 2
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 3
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 4
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 5
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 6
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 7
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 8
PASS -> FAIL: gdb.base/multi-forks.exp: info inferior 9
PASS -> FAIL: gdb.base/multi-forks.exp: kill 6
PASS -> FAIL: gdb.base/multi-forks.exp: kill 7
PASS -> FAIL: gdb.base/multi-forks.exp: kill 8
PASS -> FAIL: gdb.base/multi-forks.exp: kill 9
PASS -> FAIL: gdb.base/multi-forks.exp: restart final
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 11
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 12
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 13
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 14
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 15
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 16
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 3
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 5
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 6
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 7
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 8
PASS -> FAIL: gdb.base/multi-forks.exp: run to exit 9
PASS -> FAIL: gdb.base/new-ui-echo.exp: extra console as driver: print on extra console echoes
PASS -> FAIL: gdb.base/new-ui-echo.exp: extra console as driver: run to breakpoint on extra console
PASS -> FAIL: gdb.base/new-ui-echo.exp: main console as driver: print on extra console echoes
PASS -> FAIL: gdb.base/new-ui-echo.exp: main console as driver: print on main console echoes
PASS -> FAIL: gdb.base/new-ui-echo.exp: main console as driver: run to breakpoint on main console
new FAIL: gdb.base/pending.exp:
PASS -> FAIL: gdb.base/pending.exp: continue to resolved breakpoint 1
PASS -> FAIL: gdb.base/pending.exp: continue to resolved breakpoint 2
PASS -> FAIL: gdb.base/pending.exp: continue to resolved breakpoint 3
new FAIL: gdb.base/pending.exp: info breakpoints
PASS -> FAIL: gdb.base/pending.exp: re-enabling pending breakpoint that can resolve instantly
PASS -> FAIL: gdb.base/pending.exp: run to resolved breakpoint 1
PASS -> FAIL: gdb.base/pending.exp: running to main
PASS -> UNRESOLVED: gdb.base/pending.exp: set imaginary pending breakpoint
PASS -> FAIL: gdb.base/pending.exp: verify pending breakpoint after restart
PASS -> FAIL: gdb.base/pie-fork.exp: test_no_detach_on_fork: continue
PASS -> FAIL: gdb.base/pie-fork.exp: test_no_detach_on_fork: thread 2.1
PASS -> FAIL: gdb.base/reread.exp: opts= "" "" : continue until exit at second pass
PASS -> FAIL: gdb.base/reread.exp: opts= "" "" : run to foo
PASS -> FAIL: gdb.base/reread.exp: opts= "" "" : second pass: run to foo
new FAIL: gdb.base/reread.exp: opts= "" "" : shell sleep 1
PASS -> UNRESOLVED: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : breakpoint foo in first file
PASS -> FAIL: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : continue until exit at second pass
PASS -> FAIL: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : run to foo
PASS -> FAIL: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : second pass: run to foo
new FAIL: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : shell sleep 1
PASS -> FAIL: gdb.base/sepdebug.exp: Temporary breakpoint info
PASS -> FAIL: gdb.base/sepdebug.exp: backtrace from factorial
PASS -> FAIL: gdb.base/sepdebug.exp: breakpoint offset +1
PASS -> FAIL: gdb.base/sepdebug.exp: build-id: run until breakpoint set at small function, optimized file
PASS -> FAIL: gdb.base/sepdebug.exp: build-id: run until function breakpoint, optimized file
PASS -> FAIL: gdb.base/sepdebug.exp: continue to factorial
PASS -> FAIL: gdb.base/sepdebug.exp: continue until exit at recursive next test
PASS -> FAIL: gdb.base/sepdebug.exp: debuglink: run until breakpoint set at small function, optimized file
PASS -> FAIL: gdb.base/sepdebug.exp: debuglink: run until function breakpoint, optimized file
new FAIL: gdb.base/sepdebug.exp: info breakpoints
PASS -> FAIL: gdb.base/sepdebug.exp: multiple-dirs: run until function breakpoint, optimized file
PASS -> UNRESOLVED: gdb.base/sepdebug.exp: next over recursive call
PASS -> FAIL: gdb.base/sepdebug.exp: next to recursive call
PASS -> FAIL: gdb.base/sepdebug.exp: run to factorial
PASS -> FAIL: gdb.base/sepdebug.exp: run until breakpoint set at a line number
PASS -> FAIL: gdb.base/sepdebug.exp: run until file:function
PASS -> FAIL: gdb.base/sepdebug.exp: run until file:linenum breakpoint
PASS -> FAIL: gdb.base/sepdebug.exp: run until function breakpoint
PASS -> FAIL: gdb.base/sepdebug.exp: run until quoted breakpoint
PASS -> FAIL: gdb.base/sepdebug.exp: step onto breakpoint
PASS -> UNRESOLVED: gdb.base/sepdebug.exp: temporary breakpoint function
PASS -> FAIL: gdb.base/shlib-call.exp: continue until exit
PASS -> FAIL: gdb.base/shlib-call.exp: re-run to bp in shared library
PASS -> FAIL: gdb.base/shlib-call.exp: run to bp in shared library
new FAIL: gdb.base/sigbpt.exp:
PASS -> FAIL: gdb.base/sigbpt.exp: cont bp after segv; continue to keeper
PASS -> FAIL: gdb.base/sigbpt.exp: cont bp before and after segv; clear breakpoint 0 of 3
PASS -> FAIL: gdb.base/sigbpt.exp: cont bp before and after segv; clear breakpoint 1 of 3
PASS -> FAIL: gdb.base/sigbpt.exp: cont bp before and after segv; continue to breakpoint at fault
PASS -> FAIL: gdb.base/sigbpt.exp: cont bp before and after segv; continue to keeper
PASS -> FAIL: gdb.base/sigbpt.exp: cont bp before and after segv; pass SIGSEGV
PASS -> FAIL: gdb.base/sigbpt.exp: cont bp before and after segv; set breakpoint 1 of 3
PASS -> FAIL: gdb.base/sigbpt.exp: cont bp before and after segv; stepi fault
PASS -> FAIL: gdb.base/sigbpt.exp: cont; clear breakpoint 0 of 1
PASS -> FAIL: gdb.base/sigbpt.exp: cont; continue to breakpoint at fault
PASS -> FAIL: gdb.base/sigbpt.exp: cont; continue to keeper
PASS -> FAIL: gdb.base/sigbpt.exp: cont; set breakpoint 0 of 1
PASS -> FAIL: gdb.base/sigbpt.exp: cont; stepi fault
PASS -> FAIL: gdb.base/sigbpt.exp: rerun to main
PASS -> FAIL: gdb.base/sigbpt.exp: stepi bp at segv; clear breakpoint 0 of 1
PASS -> FAIL: gdb.base/sigbpt.exp: stepi bp at segv; continue to keeper
PASS -> FAIL: gdb.base/sigbpt.exp: stepi bp at segv; set breakpoint 0 of 1
KFAIL -> FAIL: gdb.base/sigbpt.exp: stepi bp at segv; stepi out of handler
PASS -> FAIL: gdb.base/sigbpt.exp: stepi; continue to keeper
KFAIL -> FAIL: gdb.base/sigbpt.exp: stepi; stepi out of handler
new FAIL: gdb.base/signull.exp:
PASS -> FAIL: gdb.base/signull.exp: code; backtrace from SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: code; backtrace from keeper through SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: code; continue to the keeper
PASS -> FAIL: gdb.base/signull.exp: code; select the pointer type
PASS -> FAIL: gdb.base/signull.exp: code; start with the bowler
PASS -> FAIL: gdb.base/signull.exp: code; take the SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: data read; backtrace from SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: data read; backtrace from keeper through SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: data read; continue to the keeper
PASS -> FAIL: gdb.base/signull.exp: data read; select the pointer type
PASS -> FAIL: gdb.base/signull.exp: data read; start with the bowler
PASS -> FAIL: gdb.base/signull.exp: data read; take the SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: data write; backtrace from SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: data write; backtrace from keeper through SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: data write; continue to the keeper
PASS -> FAIL: gdb.base/signull.exp: data write; select the pointer type
PASS -> FAIL: gdb.base/signull.exp: data write; start with the bowler
PASS -> FAIL: gdb.base/signull.exp: data write; take the SIGSEGV
PASS -> FAIL: gdb.base/signull.exp: handle SIGBUS
PASS -> FAIL: gdb.base/signull.exp: handle SIGSEGV
PASS -> FAIL: gdb.base/step-bt.exp: run to hello
PASS -> FAIL: gdb.base/step-over-exit.exp: continue to end, second time
PASS -> FAIL: gdb.base/step-over-exit.exp: continue to exit
PASS -> FAIL: gdb.base/step-over-exit.exp: continue to marker, first time
PASS -> FAIL: gdb.base/step-over-exit.exp: continue to marker, second time
PASS -> FAIL: gdb.base/step-over-exit.exp: display/i $pc
new FAIL: gdb.base/step-over-exit.exp: set breakpoint condition-evaluation target
PASS -> FAIL: gdb.base/step-over-exit.exp: set conditional break at syscall address
PASS -> FAIL: gdb.base/step-over-exit.exp: switch back to inferior 1, second time
PASS -> FAIL: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=child: break cond on target : fork: break marker
PASS -> FAIL: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=child: break cond on target : fork: continue to end of inf 2
PASS -> FAIL: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=child: break cond on target : fork: continue to marker
PASS -> FAIL: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=child: break cond on target : fork: inferior 1
PASS -> FAIL: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=parent: break cond on target : fork: continue to marker
PASS -> FAIL: gdb.base/unload.exp: pending breakpoint info on first run at shrfunc1
PASS -> FAIL: gdb.base/unload.exp: pending breakpoint info on second run at shrfunc1
PASS -> FAIL: gdb.base/unload.exp: rerun to shared library breakpoint
PASS -> FAIL: gdb.base/unload.exp: running program
new FAIL: gdb.base/unload.exp: setting breakpoint at unload.c:66
new FAIL: gdb.base/unload.exp: setting breakpoint at unload.c:93
PASS -> FAIL: gdb.base/vdso-warning.exp: core: save a corefile
PASS -> FAIL: gdb.base/vdso-warning.exp: run: startup
new FAIL: gdb.base/watchpoint-solib.exp:
PASS -> FAIL: gdb.base/watchpoint-solib.exp: continue to foo again
PASS -> FAIL: gdb.base/watchpoint-solib.exp: continue to watchpoint hit again
PASS -> FAIL: gdb.cp/exception.exp: run to main
PASS -> FAIL: gdb.cp/mb-inline.exp: disabling location: disable
PASS -> FAIL: gdb.cp/mb-inline.exp: disabling location: run to breakpoint
PASS -> FAIL: gdb.cp/mb-inline.exp: run to breakpoint
PASS -> FAIL: gdb.cp/mb-inline.exp: run to breakpoint 2
new UNRESOLVED: gdb.cp/mb-templates.exp: can't run to main for multi_line_foo tests.
new FAIL: gdb.cp/mb-templates.exp: disable breakpoint: disable
new FAIL: gdb.cp/mb-templates.exp: disable breakpoint: run to breakpoint
new FAIL: gdb.cp/mb-templates.exp: disabling location: disable
new FAIL: gdb.cp/mb-templates.exp: disabling location: enable
new FAIL: gdb.cp/mb-templates.exp: disabling location: run to breakpoint
PASS -> FAIL: gdb.cp/mb-templates.exp: initial condition: run to breakpoint
new FAIL: gdb.cp/mb-templates.exp: initial condition: run to breakpoint 2
new FAIL: gdb.cp/mb-templates.exp: instantiation: run to breakpoint
new FAIL: gdb.cp/mb-templates.exp: instantiation: run to breakpoint 2
new UNRESOLVED: gdb.cp/mb-templates.exp: kill
new FAIL: gdb.cp/mb-templates.exp: separate condition: run to breakpoint
new FAIL: gdb.cp/mb-templates.exp: separate condition: run to breakpoint 2
PASS -> FAIL: gdb.cp/parse-lang.exp: breakpoint hit
PASS -> FAIL: gdb.cp/re-set-overloaded.exp: breakpoint resolved
PASS -> FAIL: gdb.cp/re-set-overloaded.exp: start
PASS -> FAIL: gdb.dwarf2/dw2-opt-structptr.exp: mi: run to main
PASS -> FAIL: gdb.go/chan.exp: disable
PASS -> FAIL: gdb.go/chan.exp: going to first breakpoint
PASS -> FAIL: gdb.go/chan.exp: going to second breakpoint
new FAIL: gdb.go/chan.exp: setting breakpoint at chan.go:9
PASS -> FAIL: gdb.go/handcall.exp: print add
PASS -> FAIL: gdb.go/handcall.exp: print main.add
PASS -> FAIL: gdb.go/hello.exp: going to first breakpoint
new FAIL: gdb.go/hello.exp: setting breakpoint at hello.go:10
PASS -> FAIL: gdb.go/integers.exp: going to first breakpoint
PASS -> FAIL: gdb.go/integers.exp: print i before assigned to 1
new FAIL: gdb.go/integers.exp: setting breakpoint at integers.go:12
new FAIL: gdb.go/methods.exp: setting breakpoint at main.T.Foo
PASS -> FAIL: gdb.go/package.exp: going to first breakpoint
new FAIL: gdb.go/package.exp: setting breakpoint at package2.Foo
PASS -> FAIL: gdb.go/strings.exp: print "abc" + "def"
PASS -> FAIL: gdb.go/unsafe.exp: print unsafe.Sizeof
PASS -> UNRESOLVED: gdb.linespec/break-ask.exp: 3
PASS -> UNRESOLVED: gdb.linespec/break-ask.exp: break twodup relative other
PASS -> FAIL: gdb.linespec/break-ask.exp: continue to breakpoint: body_elsewhere
PASS -> FAIL: gdb.linespec/break-ask.exp: continue to breakpoint: body_elsewhere other
PASS -> FAIL: gdb.linespec/break-ask.exp: expect breakpoint
PASS -> FAIL: gdb.linespec/break-ask.exp: expect breakpoint other
PASS -> FAIL: gdb.linespec/break-ask.exp: info source
PASS -> FAIL: gdb.linespec/break-ask.exp: info source other
PASS -> FAIL: gdb.mi/dw2-ref-missing-frame.exp: mi runto func_loopfb_marker
PASS -> FAIL: gdb.mi/dw2-ref-missing-frame.exp: mi runto func_nofb_marker
PASS -> FAIL: gdb.mi/dw2-ref-missing-frame.exp: test func_loopfb_var
PASS -> FAIL: gdb.mi/dw2-ref-missing-frame.exp: test func_nofb_marker
PASS -> FAIL: gdb.mi/gdb2549.exp: mi runto main
PASS -> FAIL: gdb.mi/gdb2549.exp: register values d
PASS -> FAIL: gdb.mi/gdb2549.exp: register values f
PASS -> FAIL: gdb.mi/gdb2549.exp: register values o
PASS -> FAIL: gdb.mi/gdb2549.exp: register values t
PASS -> FAIL: gdb.mi/gdb2549.exp: register values x
PASS -> FAIL: gdb.mi/gdb669.exp: mi runto main
PASS -> FAIL: gdb.mi/gdb669.exp: next, try 0
PASS -> FAIL: gdb.mi/gdb701.exp: create fooPtr
PASS -> FAIL: gdb.mi/gdb701.exp: mi runto main
PASS -> FAIL: gdb.mi/gdb701.exp: step over "foo = 0"
PASS -> FAIL: gdb.mi/gdb792.exp: create var for class A
PASS -> FAIL: gdb.mi/gdb792.exp: list children of A.private
PASS -> FAIL: gdb.mi/gdb792.exp: list children of A.protected
PASS -> FAIL: gdb.mi/gdb792.exp: list children of A.public
PASS -> FAIL: gdb.mi/gdb792.exp: list children of class A
PASS -> FAIL: gdb.mi/gdb792.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-async-run.exp: expect interrupt
PASS -> FAIL: gdb.mi/mi-async-run.exp: send interrupt command
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint at nonexistent function
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint commands: check that commands are set
new FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint commands: continue
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint commands: insert breakpoint at basics.c:callee2
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint commands: insert breakpoint at basics.c:callee2, again
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint commands: set commands
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint with garbage after location
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: create varobj for function call
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: mi runto main
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: run to breakpoint with ignore count
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: test disabled creation
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: test disabled creation: cleanup
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=main: update varobj for function call
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint at nonexistent function
new FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint commands: continue
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint commands: insert breakpoint at basics.c:callee2
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint commands: insert breakpoint at basics.c:callee2, again
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint commands: set commands
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint with garbage after location
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: create varobj for function call
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: mi runto main
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: run to breakpoint with ignore count
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: test disabled creation
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: test disabled creation: cleanup
PASS -> FAIL: gdb.mi/mi-break.exp: mi-mode=separate: update varobj for function call
PASS -> FAIL: gdb.mi/mi-breakpoint-changed.exp: test_insert_delete_modify: mi runto main
PASS -> FAIL: gdb.mi/mi-breakpoint-changed.exp: test_pending_resolved: pending resolved: breakpoint on pendfunc1 resolved
PASS -> FAIL: gdb.mi/mi-breakpoint-location-ena-dis.exp: -break-disable 2.2
PASS -> FAIL: gdb.mi/mi-breakpoint-location-ena-dis.exp: -break-enable 2.2
PASS -> FAIL: gdb.mi/mi-breakpoint-location-ena-dis.exp: break add
PASS -> FAIL: gdb.mi/mi-breakpoint-location-ena-dis.exp: dis 2.2
PASS -> FAIL: gdb.mi/mi-breakpoint-location-ena-dis.exp: en 2.2
PASS -> FAIL: gdb.mi/mi-breakpoint-location-ena-dis.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-catch-load.exp: catch-load: auto-solib-add on
PASS -> FAIL: gdb.mi/mi-catch-load.exp: catch-unload: auto-solib-add on
PASS -> FAIL: gdb.mi/mi-catch-load.exp: catch-unload: catch unload
new FAIL: gdb.mi/mi-catch-load.exp: catch-unload: continue
PASS -> FAIL: gdb.mi/mi-catch-load.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "break callee4"
PASS -> FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "info break"
PASS -> FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "set args foobar"
PASS -> FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "set listsize 1"
PASS -> FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "show args"
PASS -> FAIL: gdb.mi/mi-cli.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-cmd-param-changed.exp: cmd param: "set scheduler-locking off"
PASS -> FAIL: gdb.mi/mi-cmd-param-changed.exp: cmd param: "set scheduler-locking on"
PASS -> FAIL: gdb.mi/mi-cmd-param-changed.exp: cmd param: "set scheduler-locking step"
PASS -> FAIL: gdb.mi/mi-cmd-param-changed.exp: cmd param: interpreter-exec "set scheduler-locking on"
PASS -> FAIL: gdb.mi/mi-cmd-param-changed.exp: cmd param: mi runto main
PASS -> FAIL: gdb.mi/mi-condbreak-call-thr-state.exp: mt: insert conditional breakpoint
PASS -> FAIL: gdb.mi/mi-condbreak-call-thr-state.exp: mt: mi runto test
PASS -> FAIL: gdb.mi/mi-condbreak-call-thr-state.exp: st: mi runto test
PASS -> FAIL: gdb.mi/mi-console.exp: Testing console output
PASS -> FAIL: gdb.mi/mi-console.exp: finished step over hello
PASS -> FAIL: gdb.mi/mi-console.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-detach.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-disassemble.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-dprintf-pending.exp: mi dprintf
PASS -> FAIL: gdb.mi/mi-dprintf.exp: call: mi 1st dprintf
PASS -> FAIL: gdb.mi/mi-dprintf.exp: fprintf: mi 1st dprintf
PASS -> FAIL: gdb.mi/mi-dprintf.exp: gdb: mi 1st dprintf
PASS -> FAIL: gdb.mi/mi-dprintf.exp: invalid explicit dprintf
new FAIL: gdb.mi/mi-dprintf.exp: mi 1st dprintf continue, agent
PASS -> FAIL: gdb.mi/mi-dprintf.exp: mi 1st dprintf, agent
new FAIL: gdb.mi/mi-dprintf.exp: mi 2nd dprintf continue, agent
PASS -> FAIL: gdb.mi/mi-dprintf.exp: mi expect stop
PASS -> FAIL: gdb.mi/mi-dprintf.exp: mi info dprintf second time
PASS -> FAIL: gdb.mi/mi-dprintf.exp: mi insert breakpoint without format string
PASS -> FAIL: gdb.mi/mi-dprintf.exp: mi insert dprintf dp_location1
PASS -> UNRESOLVED: gdb.mi/mi-dprintf.exp: mi insert dprintf foo
PASS -> FAIL: gdb.mi/mi-dprintf.exp: mi insert second breakpoint without format string
PASS -> FAIL: gdb.mi/mi-dprintf.exp: mi insert without location
PASS -> FAIL: gdb.mi/mi-dprintf.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-eval.exp: eval &A
PASS -> FAIL: gdb.mi/mi-eval.exp: eval A
PASS -> FAIL: gdb.mi/mi-eval.exp: eval A + 3
PASS -> FAIL: gdb.mi/mi-eval.exp: eval A+3
PASS -> FAIL: gdb.mi/mi-eval.exp: mi runto callee4
PASS -> FAIL: gdb.mi/mi-eval.exp: next at callee4
PASS -> FAIL: gdb.mi/mi-exit-code.exp: first run: -list-thread-groups after exit shows exit-code
PASS -> FAIL: gdb.mi/mi-exit-code.exp: first run: -list-thread-groups during run shows no exit-code
new FAIL: gdb.mi/mi-exit-code.exp: first run: continue to end
new FAIL: gdb.mi/mi-exit-code.exp: first run: continuing to inferior exit
PASS -> FAIL: gdb.mi/mi-exit-code.exp: first run: mi runto main
PASS -> FAIL: gdb.mi/mi-exit-code.exp: second run: -list-thread-groups after exit shows exit-code
PASS -> FAIL: gdb.mi/mi-exit-code.exp: second run: -list-thread-groups during run shows no exit-code
PASS -> UNRESOLVED: gdb.mi/mi-exit-code.exp: second run: breakpoint at main
new FAIL: gdb.mi/mi-exit-code.exp: second run: continuing to inferior exit
PASS -> FAIL: gdb.mi/mi-exit-code.exp: second run: exit with code
PASS -> FAIL: gdb.mi/mi-exit-code.exp: second run: mi runto main
PASS -> FAIL: gdb.mi/mi-exit-code.exp: second run: write exit code
PASS -> FAIL: gdb.mi/mi-fill-memory.exp: memory successfully filled
PASS -> FAIL: gdb.mi/mi-fill-memory.exp: memory successfully written
PASS -> FAIL: gdb.mi/mi-fill-memory.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-fill-memory.exp: next at main
PASS -> FAIL: gdb.mi/mi-fill-memory.exp: no arguments
PASS -> FAIL: gdb.mi/mi-fill-memory.exp: one argument missing
PASS -> FAIL: gdb.mi/mi-fill-memory.exp: pattern correctly read from memory
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_fixed_varobj_test: breakpoint hit in callee3
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_fixed_varobj_test: create varobj for $pc in frame 0
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_fixed_varobj_test: insert breakpoint at basics.c:callee3
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_fixed_varobj_test: mi runto main
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_floating_varobj_test: -var-update for frame 1
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_floating_varobj_test: breakpoint hit in callee1
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_floating_varobj_test: create varobj for pc in frame 0
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_floating_varobj_test: insert breakpoint at basics.c:callee1
PASS -> FAIL: gdb.mi/mi-frame-regs.exp: do_floating_varobj_test: mi runto main
new FAIL: gdb.mi/mi-inheritance-syntax-error.exp: -data-evaluate-expression kill\n
PASS -> FAIL: gdb.mi/mi-inheritance-syntax-error.exp: -var-info-path-expression var1.A
PASS -> FAIL: gdb.mi/mi-inheritance-syntax-error.exp: create var for THIS
PASS -> FAIL: gdb.mi/mi-inheritance-syntax-error.exp: list children of THIS
PASS -> FAIL: gdb.mi/mi-inheritance-syntax-error.exp: mi runto C::testLocation
PASS -> FAIL: gdb.mi/mi-linespec-err-cp.exp: breakpoint hit
PASS -> FAIL: gdb.mi/mi-linespec-err-cp.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-linespec-err-cp.exp: set breakpoint
PASS -> FAIL: gdb.mi/mi-logging.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-memory-changed.exp: change C thru. -data-write-memory-bytes
PASS -> FAIL: gdb.mi/mi-memory-changed.exp: change C thru. varobj
PASS -> FAIL: gdb.mi/mi-memory-changed.exp: continue to callee4
PASS -> FAIL: gdb.mi/mi-memory-changed.exp: create objvar for C
PASS -> FAIL: gdb.mi/mi-memory-changed.exp: get address of main
PASS -> FAIL: gdb.mi/mi-memory-changed.exp: set var C = 4
PASS -> FAIL: gdb.mi/mi-nonstop-exit.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-nonstop.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-ns-stale-regcache.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-nsintrall.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-nsmoribund.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-nsthrexec.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-pending.exp: MI pending breakpoint on pendfunc3
PASS -> FAIL: gdb.mi/mi-pending.exp: Run till MI pending breakpoint on pendfunc1
PASS -> FAIL: gdb.mi/mi-pending.exp: Run till MI pending breakpoint on pendfunc2 with x==4
PASS -> FAIL: gdb.mi/mi-pending.exp: Run till MI pending breakpoint on thread_func
new FAIL: gdb.mi/mi-pending.exp: continuing execution to skip conditional bp
new FAIL: gdb.mi/mi-pending.exp: continuing execution to thread condition
PASS -> FAIL: gdb.mi/mi-pending.exp: delete breakpoint 3
PASS -> FAIL: gdb.mi/mi-pthreads.exp: -thread_list_ids
PASS -> FAIL: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select
PASS -> FAIL: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 123456789
PASS -> FAIL: gdb.mi/mi-pthreads.exp: finding threads in MI output
PASS -> FAIL: gdb.mi/mi-pthreads.exp: mi runto done_making_threads
PASS -> FAIL: gdb.mi/mi-read-memory.exp: 3x2, one byte
PASS -> FAIL: gdb.mi/mi-read-memory.exp: 3x2, one byte offset by -6
PASS -> FAIL: gdb.mi/mi-read-memory.exp: expression in quotes
PASS -> FAIL: gdb.mi/mi-read-memory.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-read-memory.exp: next at main
PASS -> FAIL: gdb.mi/mi-read-memory.exp: no arguments
PASS -> FAIL: gdb.mi/mi-record-changed.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-record-changed.exp: record
PASS -> FAIL: gdb.mi/mi-record-changed.exp: record end
PASS -> FAIL: gdb.mi/mi-record-changed.exp: target record
PASS -> FAIL: gdb.mi/mi-return.exp: delete all breakpoints
PASS -> FAIL: gdb.mi/mi-return.exp: mi runto callee4
PASS -> FAIL: gdb.mi/mi-reverse.exp: Turn on process record
PASS -> FAIL: gdb.mi/mi-reverse.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-simplerun.exp: continue to end
PASS -> FAIL: gdb.mi/mi-simplerun.exp: exec-finish
PASS -> FAIL: gdb.mi/mi-simplerun.exp: next at main
PASS -> FAIL: gdb.mi/mi-simplerun.exp: run to main
PASS -> FAIL: gdb.mi/mi-simplerun.exp: step at main
PASS -> FAIL: gdb.mi/mi-simplerun.exp: step to callee4
PASS -> FAIL: gdb.mi/mi-solib.exp: test_file_list_shared_libraries: get the list of shared libraries
PASS -> FAIL: gdb.mi/mi-solib.exp: test_file_list_shared_libraries: mi runto main
PASS -> FAIL: gdb.mi/mi-stack.exp: mi runto callee4
PASS -> FAIL: gdb.mi/mi-stack.exp: run to 27
PASS -> FAIL: gdb.mi/mi-stack.exp: stack frame listing
PASS -> FAIL: gdb.mi/mi-stack.exp: stack frame listing 1 1
PASS -> FAIL: gdb.mi/mi-stack.exp: stack frame listing 1 3
PASS -> FAIL: gdb.mi/mi-stack.exp: stack frame listing wrong
new FAIL: gdb.mi/mi-stack.exp: wait for stop
PASS -> FAIL: gdb.mi/mi-stepi.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-stepi.exp: next-instruction at main
PASS -> FAIL: gdb.mi/mi-stepi.exp: step-instruction at main
PASS -> FAIL: gdb.mi/mi-stepn.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-syn-frame.exp: backtrace from inferior function stopped at bp, showing gdb dummy frame
PASS -> FAIL: gdb.mi/mi-syn-frame.exp: call inferior's function with a breakpoint set in it
PASS -> FAIL: gdb.mi/mi-syn-frame.exp: insert breakpoint foo
PASS -> FAIL: gdb.mi/mi-syn-frame.exp: mi runto main
new FAIL: gdb.mi/mi-syn-frame.exp: testing exec continue
PASS -> FAIL: gdb.mi/mi-threads-interrupt.exp: check thread states
new FAIL: gdb.mi/mi-threads-interrupt.exp: continue
PASS -> FAIL: gdb.mi/mi-threads-interrupt.exp: interrupt reported
PASS -> FAIL: gdb.mi/mi-threads-interrupt.exp: mi runto all_threads_created
PASS -> FAIL: gdb.mi/mi-until.exp: break-delete 1
PASS -> FAIL: gdb.mi/mi-until.exp: run to main
PASS -> FAIL: gdb.mi/mi-until.exp: until after current function
KFAIL -> FAIL: gdb.mi/mi-until.exp: until after while loop
PASS -> FAIL: gdb.mi/mi-until.exp: until line number
PASS -> FAIL: gdb.mi/mi-until.exp: until line number:file
PASS -> FAIL: gdb.mi/mi-var-block.exp: create local variable cb
PASS -> FAIL: gdb.mi/mi-var-block.exp: create local variable foo
PASS -> FAIL: gdb.mi/mi-var-block.exp: delete var foo 1
PASS -> FAIL: gdb.mi/mi-var-block.exp: mi runto do_block_tests
PASS -> FAIL: gdb.mi/mi-var-block.exp: step at do_block_test 1
PASS -> FAIL: gdb.mi/mi-var-block.exp: step at do_block_test 2
PASS -> FAIL: gdb.mi/mi-var-block.exp: try to create local variable foo
PASS -> FAIL: gdb.mi/mi-var-child-f.exp: create local variable array
PASS -> FAIL: gdb.mi/mi-var-child-f.exp: get children of array
PASS -> FAIL: gdb.mi/mi-var-child-f.exp: mi runto MAIN__
new FAIL: gdb.mi/mi-var-child.exp: child_deletion: go to line 339
new FAIL: gdb.mi/mi-var-child.exp: child_deletion: step over 339
PASS -> FAIL: gdb.mi/mi-var-child.exp: create local variable struct_declarations
PASS -> FAIL: gdb.mi/mi-var-child.exp: get children of struct_declarations
PASS -> FAIL: gdb.mi/mi-var-child.exp: mi runto do_children_tests
PASS -> FAIL: gdb.mi/mi-var-child.exp: run to 229
new FAIL: gdb.mi/mi-var-child.exp: wait for stop
new FAIL: gdb.mi/mi-var-cmd.exp: bitfield: go to line 526
new FAIL: gdb.mi/mi-var-cmd.exp: bitfield: step over 526
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: breakpoint at do_locals_tests
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: check F inside callee
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: continue to where i is initialized
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: create local variable lcharacter
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: create local variable lfloat
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: create local variable linteger
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: create local variable llong
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: create local variable lpcharacter
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: create local variable lpinteger
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: create local variable lplong
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: create null_ptr
new FAIL: gdb.mi/mi-var-cmd.exp: floating: go to line 469
new FAIL: gdb.mi/mi-var-cmd.exp: floating: step over 469
new FAIL: gdb.mi/mi-var-cmd.exp: frozen: go to line 367
new FAIL: gdb.mi/mi-var-cmd.exp: frozen: step over 367
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: in-and-out-of-scope: check initial value
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: in-and-out-of-scope: create varobj
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: in-and-out-of-scope: in scope now
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: in-and-out-of-scope: in scope now, not changed
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: in-and-out-of-scope: out of scope now
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: in-and-out-of-scope: out of scope now, not changed
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: mi runto do_locals_tests
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: run to 148
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: run to var-cmd.c:469
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: run to var-cmd.c:526
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: update F inside callee
PASS -> FAIL: gdb.mi/mi-var-cmd.exp: update null_ptr
new FAIL: gdb.mi/mi-var-cmd.exp: wait for stop
new FAIL: gdb.mi/mi-var-cp.exp: base_in_reference: go to line 45
new FAIL: gdb.mi/mi-var-cp.exp: base_in_reference: step over 45
PASS -> FAIL: gdb.mi/mi-var-cp.exp: break in anonymous_structs_and_unions
new FAIL: gdb.mi/mi-var-cp.exp: path_expression: go to line 144
new FAIL: gdb.mi/mi-var-cp.exp: path_expression: step over 144
new FAIL: gdb.mi/mi-var-cp.exp: reference_to_pointer: go to line 81
new FAIL: gdb.mi/mi-var-cp.exp: reference_to_pointer: step over 81
new FAIL: gdb.mi/mi-var-cp.exp: reference_to_struct: go to line 104
new FAIL: gdb.mi/mi-var-cp.exp: reference_to_struct: step over 104
new FAIL: gdb.mi/mi-var-cp.exp: reference_update: go to line 19
new FAIL: gdb.mi/mi-var-cp.exp: reference_update: step over 19
PASS -> FAIL: gdb.mi/mi-var-cp.exp: run to mi-var-cp.cc:104
PASS -> FAIL: gdb.mi/mi-var-cp.exp: run to mi-var-cp.cc:144
PASS -> FAIL: gdb.mi/mi-var-cp.exp: run to mi-var-cp.cc:45
PASS -> FAIL: gdb.mi/mi-var-cp.exp: run to mi-var-cp.cc:81
new FAIL: gdb.mi/mi-var-cp.exp: wait for stop
PASS -> FAIL: gdb.mi/mi-var-create-rtti.exp: -var-create sp1 * $sp
PASS -> FAIL: gdb.mi/mi-var-create-rtti.exp: -var-create sp2 @ $sp
PASS -> FAIL: gdb.mi/mi-var-create-rtti.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-var-display.exp: assing to variable bar
PASS -> FAIL: gdb.mi/mi-var-display.exp: create local variable bar
PASS -> FAIL: gdb.mi/mi-var-display.exp: eval variable bar
PASS -> FAIL: gdb.mi/mi-var-display.exp: eval variable bar with new format
PASS -> FAIL: gdb.mi/mi-var-display.exp: info type variable bar
PASS -> FAIL: gdb.mi/mi-var-display.exp: run to main
PASS -> FAIL: gdb.mi/mi-var-display.exp: set format variable bar in decimal
PASS -> FAIL: gdb.mi/mi-var-display.exp: set format variable bar in hex
PASS -> FAIL: gdb.mi/mi-var-display.exp: set format variable bar in zero-padded hexadecimal
PASS -> FAIL: gdb.mi/mi-var-display.exp: show format variable bar
PASS -> UNRESOLVED: gdb.mi/mi-var-invalidate.exp: breakpoint at main
PASS -> FAIL: gdb.mi/mi-var-invalidate.exp: create floating variable
PASS -> FAIL: gdb.mi/mi-var-invalidate.exp: create local variable linteger
PASS -> FAIL: gdb.mi/mi-var-invalidate.exp: global_simple still alive
PASS -> FAIL: gdb.mi/mi-var-invalidate.exp: linteger not anymore in scope due to binary changes
PASS -> UNRESOLVED: gdb.mi/mi-var-invalidate.exp: linteger not valid anymore due to binary changes
PASS -> FAIL: gdb.mi/mi-var-invalidate.exp: mi runto do_locals_tests
PASS -> FAIL: gdb.mi/mi-var-invalidate.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-var-invalidate.exp: set format variable float_simple
PASS -> FAIL: gdb.mi/mi-var-invalidate.exp: type simpleton for valid variable global_simple
PASS -> FAIL: gdb.mi/mi-var-list-children-invalid-grandchild.exp: create variable object
PASS -> FAIL: gdb.mi/mi-var-list-children-invalid-grandchild.exp: list children #1
PASS -> FAIL: gdb.mi/mi-var-list-children-invalid-grandchild.exp: list children #2
PASS -> FAIL: gdb.mi/mi-var-list-children-invalid-grandchild.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-var-list-children-invalid-grandchild.exp: run to 41
PASS -> FAIL: gdb.mi/mi-var-list-children-invalid-grandchild.exp: run to 43
PASS -> FAIL: gdb.mi/mi-var-list-children-invalid-grandchild.exp: update variable object
new FAIL: gdb.mi/mi-var-list-children-invalid-grandchild.exp: wait for stop
PASS -> FAIL: gdb.mi/mi-var-rtti.exp: run to mi-var-rtti.cc:148
PASS -> FAIL: gdb.mi/mi-var-rtti.exp: run to mi-var-rtti.cc:201
PASS -> FAIL: gdb.mi/mi-var-rtti.exp: run to mi-var-rtti.cc:250
PASS -> FAIL: gdb.mi/mi-var-rtti.exp: run to mi-var-rtti.cc:306
PASS -> FAIL: gdb.mi/mi-var-rtti.exp: run to mi-var-rtti.cc:63
PASS -> FAIL: gdb.mi/mi-var-rtti.exp: run to mi-var-rtti.cc:93
new FAIL: gdb.mi/mi-var-rtti.exp: skip_type_update_when_not_use_rtti: go to line 306
new FAIL: gdb.mi/mi-var-rtti.exp: skip_type_update_when_not_use_rtti: step over 306
new FAIL: gdb.mi/mi-var-rtti.exp: type_update_when_use_rtti: go to line 250
new FAIL: gdb.mi/mi-var-rtti.exp: type_update_when_use_rtti: step over 250
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_for_ptr: go to line 36
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_for_ptr: step over 36
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_for_ptr_child: go to line 93
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_for_ptr_child: step over 93
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_for_ref: go to line 63
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_for_ref: step over 63
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_for_ref_child: go to line 148
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_for_ref_child: step over 148
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_with_multiple_inheritence: go to line 201
new FAIL: gdb.mi/mi-var-rtti.exp: use_rtti_with_multiple_inheritence: step over 201
new FAIL: gdb.mi/mi-var-rtti.exp: wait for stop
PASS -> FAIL: gdb.mi/mi-vla-c99.exp: evaluate complete vla
PASS -> FAIL: gdb.mi/mi-vla-c99.exp: evaluate vla[0]
PASS -> FAIL: gdb.mi/mi-vla-c99.exp: evaluate vla[2]
PASS -> FAIL: gdb.mi/mi-vla-c99.exp: evaluate vla[4]
PASS -> FAIL: gdb.mi/mi-vla-c99.exp: run to breakpoint at line 28
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: create local variable pvla2_associated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: create local variable vla1_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: create local variable vla1_not_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: eval variable vla1_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: eval variable vla1_not_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate allocated vla
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate associated vla
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate filled vla
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate filled vla, contents modified
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate filled vla, filled all 1s
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate not allocated vla, after deallocation
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate not allocated vla, before allocation
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate not associated vla
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: evaluate vla pointer set to null
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: get children of vla1_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: get children of vla1_not_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: info type variable pvla2_associated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: info type variable vla1_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: info type variable vla1_not_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: insert breakpoint at line 24
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: insert breakpoint at line 30
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: insert breakpoint at line 31
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: insert breakpoint at line 36
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: insert breakpoint at line 37
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: run to breakpoint at line 23
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: run to breakpoint at line 24
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: run to breakpoint at line 27
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: run to breakpoint at line 30
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: run to breakpoint at line 31
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: run to breakpoint at line 36
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: run to breakpoint at line 37
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: run to breakpoint at line 42
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: show format variable pvla2_associated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: show format variable vla1_allocated
PASS -> FAIL: gdb.mi/mi-vla-fortran.exp: show format variable vla1_not_allocated
PASS -> FAIL: gdb.mi/mi-watch-nonstop.exp: mi runto main
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=main: wp-type=hw: break-watch operation
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=main: wp-type=hw: list of watchpoints
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=main: wp-type=hw: mi runto callee4
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=main: wp-type=hw: watchpoint trigger
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=main: wp-type=sw: break-watch operation
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=main: wp-type=sw: list of watchpoints
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=main: wp-type=sw: mi runto callee4
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=main: wp-type=sw: watchpoint trigger
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=separate: wp-type=hw: break-watch operation
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=separate: wp-type=hw: list of watchpoints
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=separate: wp-type=hw: mi runto callee4
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=separate: wp-type=hw: watchpoint trigger
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=separate: wp-type=sw: break-watch operation
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=separate: wp-type=sw: list of watchpoints
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=separate: wp-type=sw: mi runto callee4
PASS -> FAIL: gdb.mi/mi-watch.exp: mi-mode=separate: wp-type=sw: watchpoint trigger
PASS -> FAIL: gdb.mi/mi2-var-child.exp: mi runto do_children_tests
PASS -> FAIL: gdb.mi/mi2-var-child.exp: run to 251
PASS -> FAIL: gdb.mi/new-ui-mi-sync.exp: sync-command=continue: mi runto main
PASS -> FAIL: gdb.mi/new-ui-mi-sync.exp: sync-command=run: add-inferior
PASS -> FAIL: gdb.mi/new-ui-mi-sync.exp: sync-command=run: interrupt on the CLI
PASS -> FAIL: gdb.mi/pr11022.exp: data-write-memory &x x 4 "01": breakpoint hit
PASS -> FAIL: gdb.mi/pr11022.exp: data-write-memory &x x 4 "01": mi runto main
PASS -> FAIL: gdb.mi/pr11022.exp: data-write-memory &x x 4 "01": set breakpoint
PASS -> FAIL: gdb.mi/pr11022.exp: data-write-memory &x x 4 "01": watchpoint hit
PASS -> FAIL: gdb.mi/pr11022.exp: data-write-memory-bytes &x "01": breakpoint hit
PASS -> FAIL: gdb.mi/pr11022.exp: data-write-memory-bytes &x "01": mi runto main
PASS -> FAIL: gdb.mi/pr11022.exp: data-write-memory-bytes &x "01": set breakpoint
PASS -> FAIL: gdb.mi/pr11022.exp: data-write-memory-bytes &x "01": watchpoint hit
new FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=detach: can't run to child_function
new FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=exit: can't run to child_function
new FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=kill: can't run to child_function
PASS -> FAIL: gdb.opt/inline-cmds.exp: mi: breakpoint hit
PASS -> FAIL: gdb.opt/inline-cmds.exp: mi: mi runto main
PASS -> FAIL: gdb.opt/inline-cmds.exp: mi: set breakpoint
PASS -> FAIL: gdb.python/py-evthreads.exp: reached breakpoint 2
PASS -> FAIL: gdb.python/py-evthreads.exp: reached breakpoint 3
PASS -> FAIL: gdb.python/py-evthreads.exp: run to breakpoint 1
PASS -> FAIL: gdb.python/py-evthreads.exp: thread 2
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: enable frame filters
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: filtered stack list 22 24
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: filtered stack listing
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: load python file
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: mi runto main
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: run to 46
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: run to 51
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: stack-list-arguments --no-frame-filters 0
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: stack-list-arguments 0
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: stack-list-arguments 0 0 3
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: stack-list-locals --all-values
PASS -> FAIL: gdb.python/py-framefilter-mi.exp: stack-list-locals --all-values frame filters enabled
new FAIL: gdb.python/py-framefilter-mi.exp: wait for stop
PASS -> FAIL: gdb.python/py-mi-events.exp: mi runto main
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: -var-create c1 * &c1
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: -var-info-path-expression c1
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: -var-info-path-expression c1.car.atom.ival
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: -var-info-path-expression c1.cdr
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: -var-list-children c1
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: -var-list-children c1.car
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: -var-list-children c1.car.atom
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: -var-list-children c1.cdr
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: mi runto main
PASS -> FAIL: gdb.python/py-mi-var-info-path-expression.exp: run to 61
PASS -> FAIL: gdb.python/py-mi.exp: Install visualizer on a cplus_fake_child
PASS -> FAIL: gdb.python/py-mi.exp: create container varobj, no pretty-printing
PASS -> FAIL: gdb.python/py-mi.exp: create fake varobj
PASS -> FAIL: gdb.python/py-mi.exp: create nscont varobj, no pretty-printing
PASS -> FAIL: gdb.python/py-mi.exp: delete varobj
PASS -> FAIL: gdb.python/py-mi.exp: examine container children=0, no pretty-printing
PASS -> FAIL: gdb.python/py-mi.exp: examine nscont children=0, no pretty-printing
PASS -> FAIL: gdb.python/py-mi.exp: list children fake.private
PASS -> FAIL: gdb.python/py-mi.exp: list children of fake
PASS -> FAIL: gdb.python/py-mi.exp: mi runto main
PASS -> FAIL: gdb.python/py-mi.exp: run to 357
PASS -> FAIL: gdb.python/py-mi.exp: run to 380
new FAIL: gdb.python/py-mi.exp: wait for stop
PASS -> FAIL: gdb.reverse/recvmsg-reverse.exp: check recvmsg record - rdata
PASS -> FAIL: gdb.reverse/recvmsg-reverse.exp: continue to breakpoint: marker2
PASS -> FAIL: gdb.reverse/recvmsg-reverse.exp: reverse to marker1
PASS -> FAIL: gdb.reverse/recvmsg-reverse.exp: set breakpoint at marker1
PASS -> FAIL: gdb.reverse/rerun-prec.exp: restarting inferior
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 33
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 34
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 35
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 36
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 37
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 38
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 39
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 40
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 41
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 42
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 43
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 44
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 45
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 46
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 47
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 48
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 49
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 50
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 51
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 52
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 53
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 54
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 55
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 56
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 57
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 58
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 59
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 60
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 61
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 62
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to 63
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to ALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to BUS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to CHLD
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to CONT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to DANGER
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to EMT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to FPE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to GRANT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to HUP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to ILL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to IO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to LOST
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to LWP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to MSG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to PHONE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to PIPE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to POLL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to PRIO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to PROF
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to PWR
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to QUIT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to RETRACT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to SAK
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to SEGV
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to SOUND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to SYS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to TERM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to TSTP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to TTIN
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to TTOU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to URG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to USR1
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to USR2
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to VTALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to WAITING
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to WINCH
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to WIND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to XCPU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: advance to XFSZ
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: continue to sigall exit
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 33
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 34
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 35
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 36
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 37
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 38
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 39
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 40
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 41
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 42
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 43
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 44
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 45
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 46
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 47
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 48
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 49
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 50
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 51
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 52
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 53
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 54
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 55
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 56
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 57
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 58
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 59
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 60
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 61
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 62
new FAIL: gdb.reverse/sigall-precsave.exp: get signal 63
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal ABRT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal ALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal BUS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal CHLD
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal CONT
new FAIL: gdb.reverse/sigall-precsave.exp: get signal DANGER
new FAIL: gdb.reverse/sigall-precsave.exp: get signal EMT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal FPE
new FAIL: gdb.reverse/sigall-precsave.exp: get signal GRANT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal HUP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal ILL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal IO
new FAIL: gdb.reverse/sigall-precsave.exp: get signal LOST
new FAIL: gdb.reverse/sigall-precsave.exp: get signal LWP
new FAIL: gdb.reverse/sigall-precsave.exp: get signal MSG
new FAIL: gdb.reverse/sigall-precsave.exp: get signal PHONE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal PIPE
new FAIL: gdb.reverse/sigall-precsave.exp: get signal POLL
new FAIL: gdb.reverse/sigall-precsave.exp: get signal PRIO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal PROF
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal PWR
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal QUIT
new FAIL: gdb.reverse/sigall-precsave.exp: get signal RETRACT
new FAIL: gdb.reverse/sigall-precsave.exp: get signal SAK
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal SEGV
new FAIL: gdb.reverse/sigall-precsave.exp: get signal SOUND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal SYS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal TERM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal TSTP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal TTIN
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal TTOU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal URG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal USR1
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal USR2
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal VTALRM
new FAIL: gdb.reverse/sigall-precsave.exp: get signal WAITING
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal WINCH
new FAIL: gdb.reverse/sigall-precsave.exp: get signal WIND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal XCPU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: get signal XFSZ
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reload precord save file
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_33
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_34
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_35
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_36
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_37
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_38
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_39
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_40
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_41
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_42
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_43
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_44
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_45
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_46
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_47
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_48
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_49
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_50
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_51
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_52
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_53
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_54
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_55
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_56
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_57
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_58
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_59
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_60
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_61
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_62
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_63
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_ABRT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_ALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_BUS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_CHLD
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_CONT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_DANGER
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_EMT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_FPE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_GRANT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_HUP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_ILL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_IO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_LOST
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_LWP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_MSG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_PHONE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_PIPE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_POLL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_PRIO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_PROF
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_PWR
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_QUIT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_RETRACT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_SAK
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_SEGV
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_SOUND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_SYS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_TERM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_TSTP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_TTIN
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_TTOU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_URG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_USR1
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_USR2
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_VTALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_WAITING
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_WINCH
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_WIND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_XCPU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to gen_XFSZ
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 33
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 34
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 35
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 36
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 37
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 38
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 39
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 40
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 41
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 42
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 43
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 44
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 45
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 46
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 47
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 48
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 49
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 50
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 51
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 52
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 53
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 54
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 55
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 56
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 57
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 58
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 59
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 60
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 61
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 62
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of 63
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of ABRT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of ALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of BUS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of CHLD
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of CONT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of DANGER
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of EMT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of FPE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of GRANT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of HUP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of ILL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of IO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of LOST
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of LWP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of MSG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of PHONE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of PIPE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of POLL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of PRIO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of PROF
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of PWR
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of QUIT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of RETRACT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of SAK
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of SEGV
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of SOUND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of SYS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of TERM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of TSTP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of TTIN
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of TTOU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of URG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of USR1
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of USR2
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of VTALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of WAITING
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of WINCH
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of WIND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of XCPU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: reverse to handler of XFSZ
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: save process recfile
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 33
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 34
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 35
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 36
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 37
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 38
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 39
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 40
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 41
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 42
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 43
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 44
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 45
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 46
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 47
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 48
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 49
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 50
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 51
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 52
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 53
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 54
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 55
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 56
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 57
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 58
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 59
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 60
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 61
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 62
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal 63
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal ABRT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal ALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal BUS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal CHLD
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal CONT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal DANGER
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal EMT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal FPE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal GRANT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal HUP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal ILL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal IO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal LOST
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal LWP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal MSG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal PHONE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal PIPE
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal POLL
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal PRIO
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal PROF
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal PWR
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal QUIT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal RETRACT
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal SAK
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal SEGV
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal SOUND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal SYS
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal TERM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal TSTP
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal TTIN
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal TTOU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal URG
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal USR1
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal USR2
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal VTALRM
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal WAITING
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal WINCH
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal WIND
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal XCPU
PASS -> FAIL: gdb.reverse/sigall-precsave.exp: send signal XFSZ
PASS -> FAIL: gdb.server/abspath.exp: continue to main
PASS -> FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=auto: continue to main
PASS -> FAIL: gdb.server/connect-without-multi-process.exp: multiprocess=off: continue to main
PASS -> FAIL: gdb.server/ext-restart.exp: monitor exit
PASS -> FAIL: gdb.server/ext-restart.exp: restart: run to main
PASS -> FAIL: gdb.server/ext-restart.exp: restart: set remote exec-file
PASS -> FAIL: gdb.server/ext-restart.exp: restart: set remote run-packet off
PASS -> FAIL: gdb.server/ext-restart.exp: run to main
PASS -> FAIL: gdb.server/ext-run.exp: continue to main
PASS -> FAIL: gdb.server/ext-run.exp: get process list
PASS -> FAIL: gdb.server/ext-wrapper.exp: print d
PASS -> FAIL: gdb.server/ext-wrapper.exp: restart: print d
PASS -> FAIL: gdb.server/ext-wrapper.exp: restart: run to marker
PASS -> FAIL: gdb.server/ext-wrapper.exp: restart: set remote exec-file
PASS -> FAIL: gdb.server/ext-wrapper.exp: restart: set remote run-packet off
PASS -> FAIL: gdb.server/ext-wrapper.exp: run to marker
PASS -> FAIL: gdb.server/no-thread-db.exp: continue to breakpoint: after tls assignment
PASS -> FAIL: gdb.server/no-thread-db.exp: print foo
PASS -> FAIL: gdb.server/reconnect-ctrl-c.exp: first: stop with control-c
PASS -> FAIL: gdb.server/reconnect-ctrl-c.exp: second: continue for ctrl-c
PASS -> FAIL: gdb.server/reconnect-ctrl-c.exp: second: disconnect
PASS -> FAIL: gdb.server/reconnect-ctrl-c.exp: second: stop with control-c
PASS -> FAIL: gdb.server/run-without-local-binary.exp: run test program until the end
PASS -> FAIL: gdb.server/server-kill.exp: continue to breakpoint: after server_pid assignment
PASS -> FAIL: gdb.server/server-kill.exp: p server_pid
PASS -> FAIL: gdb.server/server-run.exp: continue to main
PASS -> FAIL: gdb.server/solib-list.exp: non-stop 0: p libvar
PASS -> FAIL: gdb.server/solib-list.exp: non-stop 0: sharedlibrary
PASS -> FAIL: gdb.server/solib-list.exp: non-stop 1: p libvar
PASS -> FAIL: gdb.server/solib-list.exp: non-stop 1: sharedlibrary
PASS -> FAIL: gdb.server/stop-reply-no-thread.exp: continue to main
PASS -> FAIL: gdb.server/wrapper.exp: continue to marker
PASS -> FAIL: gdb.server/wrapper.exp: print d
PASS -> FAIL: gdb.threads/execl.exp: continue across exec
PASS -> FAIL: gdb.threads/execl.exp: continue until exit
PASS -> FAIL: gdb.threads/execl.exp: info threads after exec
PASS -> FAIL: gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
PASS -> FAIL: gdb.threads/killed.exp: run program to completion
PASS -> FAIL: gdb.threads/non-ldr-exc-1.exp: lock-sched=off,non-stop=off: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-1.exp: lock-sched=off,non-stop=on: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-1.exp: lock-sched=on,non-stop=off: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-2.exp: lock-sched=off,non-stop=off: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-2.exp: lock-sched=off,non-stop=on: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-2.exp: lock-sched=on,non-stop=off: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-3.exp: lock-sched=off,non-stop=off: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-3.exp: lock-sched=off,non-stop=on: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-3.exp: lock-sched=on,non-stop=off: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-4.exp: lock-sched=off,non-stop=off: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-4.exp: lock-sched=off,non-stop=on: continue over exec
PASS -> FAIL: gdb.threads/non-ldr-exc-4.exp: lock-sched=on,non-stop=off: continue over exec
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: detach: continue
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: detach: continue to breakpoint: _exit
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: detach: detach child
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: detach: switch to parent
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: killed outside: continue to breakpoint: _exit
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: killed outside: get integer valueof "mypid"
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: watchpoint: continue to breakpoint: _exit
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: watchpoint: continue to breakpoint: child_function
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: watchpoint: detach child
new FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: watchpoint: setting breakpoint at _exit
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: watchpoint: watch globalvar
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: detach: continue to breakpoint: _exit
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: detach: detach child
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: detach: detach parent
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: detach: switch to parent
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: killed outside: continue to breakpoint: _exit
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: killed outside: get integer valueof "mypid"
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: watchpoint: continue to breakpoint: _exit
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: watchpoint: continue to breakpoint: child_function
new FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: watchpoint: setting breakpoint at _exit
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: detach: watchpoint: watch globalvar
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: detach: continue
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: detach: server exits
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: watchpoint: continue
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: watchpoint: server exits
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
PASS -> FAIL: gdb.threads/thread-execl.exp: non-stop: get to main in new image
PASS -> FAIL: gdb.threads/thread-execl.exp: schedlock off: get to main in new image
PASS -> FAIL: gdb.threads/thread-execl.exp: schedlock on: get to main in new image
PASS -> FAIL: gdb.threads/thread-execl.exp: schedlock step: get to main in new image
new FAIL: gdb.trace/actions.exp: can't run to main
PASS -> FAIL: gdb.trace/change-loc.exp: 2 trace: delete break 2
PASS -> FAIL: gdb.trace/change-loc.exp: 2 trace: run to main
new FAIL: gdb.trace/infotrace.exp: can't run to main
new FAIL: gdb.trace/mi-trace-frame-collected.exp: -target-select ctf
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: -trace-define-variable
new FAIL: gdb.trace/mi-trace-frame-collected.exp: continuing to end
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: insert tracepoint on end
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: insert tracepoint on gdb_c_test
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: insert tracepoint on gdb_recursion_test
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: live: -trace-find frame-number 0
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: live: -trace-find frame-number 1
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: live: -trace-find none
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: live: -trace-frame-collected
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: live: -trace-frame-collected --var-print-values 2 --comp-print-values --simple-values --registers-format x --memory-contents
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: mi runto main
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: save tfile trace file
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: set action
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: stop at end
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile: -trace-find frame-number 0
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile: -trace-find frame-number 1
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile: -trace-find none
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile: -trace-frame-collected
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile: -trace-frame-collected --var-print-values 2 --comp-print-values --simple-values --registers-format x --memory-contents
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: trace start
PASS -> FAIL: gdb.trace/mi-trace-frame-collected.exp: trace stop
new FAIL: gdb.trace/mi-trace-unavailable.exp: continuing to marker
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: insert tracepoint on bar
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: insert tracepoint on foo
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: insert tracepoint on marker
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: live: -trace-find frame-number 0
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: live: no: -stack-list-locals --simple-values
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: mi runto main
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: save tfile trace file
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: set action
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: set action on tracepoint 4
PASS -> FAIL: gdb.trace/mi-trace-unavailable.exp: stop at marker
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: remote: break end
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: remote: continue to end
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: remote: mi runto main
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: remote: trace start
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: remote: trace stop
PASS -> FAIL: gdb.trace/mi-tracepoint-changed.exp: pending resolved: continue to marker breakpoint
new FAIL: gdb.trace/mi-tracepoint-changed.exp: pending resolved: continuing execution to marker 1
PASS -> FAIL: gdb.trace/mi-tracepoint-changed.exp: pending resolved: trace start
PASS -> FAIL: gdb.trace/mi-tracepoint-changed.exp: reconnect: break-info 1
PASS -> FAIL: gdb.trace/mi-tsv-changed.exp: create delete modify: continue to begin breakpoint
new FAIL: gdb.trace/mi-tsv-changed.exp: create delete modify: continuing to end
PASS -> FAIL: gdb.trace/mi-tsv-changed.exp: create delete modify: trace start
PASS -> FAIL: gdb.trace/mi-tsv-changed.exp: create delete modify: tvariable $tvar3 modified
PASS -> FAIL: gdb.trace/pending.exp: trace resolved: single tracepoint info
PASS -> FAIL: gdb.trace/pending.exp: trace works: breakpoint on marker
PASS -> FAIL: gdb.trace/pending.exp: trace works: continue to marker
PASS -> FAIL: gdb.trace/pending.exp: trace works: start trace experiment
PASS -> FAIL: gdb.trace/pending.exp: trace works: tfind test frame
PASS -> FAIL: gdb.trace/pending.exp: trace works: tfind test frame 0
PASS -> FAIL: gdb.trace/pending.exp: trace works: tfind test frame 1
PASS -> FAIL: gdb.trace/pending.exp: trace works: tfind test frame 2
new FAIL: gdb.trace/while-stepping.exp: can't run to main
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Bump GDB version number to 8.3.0.DATE-git.
@ 2019-05-11 18:58 sergiodj+buildbot
2019-05-13 20:51 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-11 18:58 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 9c5d0147d8cc011808fc5e165d528a0baad7e6c4 ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: 9c5d0147d8cc011808fc5e165d528a0baad7e6c4
Bump GDB version number to 8.3.0.DATE-git.
gdb/ChangeLog:
* version.in: Set GDB version number to 8.3.0.DATE-git.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Set GDB version number to 8.3.
@ 2019-05-11 18:40 sergiodj+buildbot
2019-05-13 18:30 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-11 18:40 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 9b407598397ef8429cbf866a02745768082e49a6 ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: 9b407598397ef8429cbf866a02745768082e49a6
Set GDB version number to 8.3.
gdb/ChangeLog:
* version.in: Set GDB version number to 8.3.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix style bug when paging
@ 2019-05-08 17:50 sergiodj+buildbot
2019-05-09 0:44 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-08 17:50 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT d0e1efa6ae35091a76023bc4e32b6b1e745fa393 ***
Author: Tom Tromey <tromey@adacore.com>
Branch: gdb-8.3-branch
Commit: d0e1efa6ae35091a76023bc4e32b6b1e745fa393
Fix style bug when paging
Philippe pointed out a styling bug that would occur in some conditions
when paging:
https://sourceware.org/ml/gdb-patches/2019-04/msg00101.html
I was finally able to reproduce this, and this patch fixes the bug.
The problem occurred when text overflowed the line, causing a
pagination prompt, but when no wrap column had been set. In this
case, the current style was reset to show the prompt, but then not
reset back to the previously applied style before emitting the rest of
the line.
The fix is to record the applied style in this case, and re-apply it
afterward -- but only if the pager prompt was emitted, something that
the existing style.exp pointed out on the first, more naive, version
of the patch.
Tested on x86-64 Fedora 29.
gdb/ChangeLog
2019-05-08 Tom Tromey <tromey@adacore.com>
* utils.c (fputs_maybe_filtered): Reset style after paging, even
when no wrap column is set.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Don't derive partial_symbol from general_symbol_info
@ 2019-05-04 20:48 sergiodj+buildbot
2019-05-05 2:52 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-04 20:48 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 20555e9e40f8e5ae041ca593d72c7148d94b6565 ***
Author: Tom Tromey <tom@tromey.com>
Branch: gdb-8.3-branch
Commit: 20555e9e40f8e5ae041ca593d72c7148d94b6565
Don't derive partial_symbol from general_symbol_info
This patch partly reverts commit 8a6d42345 ("Change representation of
psymbol to flush out accessors"); specifically, it changes
partial_symbol to no longer derive from general_symbol_info.
The basic problem here is that the bcache compares objects bitwise,
and this change made it less likely that the relevant fields in the
psymbol would be fully initialized. This could be seen by running a
test under valgrind on the Fedora-i686 buildbot.
I considered a simpler patch, namely just zeroing the psymbol's
"value" field in add_psymbol_to_bcache. However, it wasn't clear to
me that this memset could not then be optimized away by the compiler.
Regression tested by the buildbot. I think this should go in 8.3 as
well.
2019-05-04 Tom Tromey <tom@tromey.com>
* psymtab.c (psymbol_name_matches, match_partial_symbol)
(lookup_partial_symbol, print_partial_symbols)
(recursively_search_psymtabs, sort_pst_symbols, psymbol_hash)
(psymbol_compare): Update.
(add_psymbol_to_bcache): Clear the entire psymbol.
(maintenance_check_psymtabs): Update.
* psympriv.h (struct partial_symbol): Don't derive from
general_symbol_info.
<obj_section, unrelocated_address, address,
set_unrelocated_address>: Update.
<ginfo>: New member.
* dwarf-index-write.c (write_psymbols, debug_names::insert)
(debug_names::write_psymbols): Update.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix compilation with mingw.org's MinGW.
@ 2019-05-03 8:22 sergiodj+buildbot
2019-05-03 14:32 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-03 8:22 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT bc694fdc3ccfb7bac93b5480dff908076c7d7893 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: bc694fdc3ccfb7bac93b5480dff908076c7d7893
Fix compilation with mingw.org's MinGW.
That flavor of MinGW assumes Windows 9X as the default target,
which doesn't expose CONSOLE_FONT_INFO stuff in Windows header
files. Since we no longer support running on Windows older
than XP anyway, requiring it at build time makes sense.
gdb/ChangeLog
2019-05-03 Eli Zaretskii <eliz@gnu.org>
* windows-nat.c [_WIN32_WINNT]: Define _WIN32_WINNT to Windows XP
level, so that various Windows header files expose the necessary
declarations and definitions.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-05-03 8:22 [binutils-gdb/gdb-8.3-branch] Fix compilation with mingw.org's MinGW sergiodj+buildbot
@ 2019-05-03 14:32 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-03 14:32 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/8022>
Commit(s) tested:
bc694fdc3ccfb7bac93b5480dff908076c7d7893
Author(s) (in the same order as the commits):
Eli Zaretskii <eliz@gnu.org>
Subject:
Fix compilation with mingw.org's MinGW.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/bc/bc694fdc3ccfb7bac93b5480dff908076c7d7893/>
*** Diff to previous build ***
============================
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=12: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=19: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=4: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=5: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=6: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=8: wait for stops
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix lookup of separate debug file on MS-Windows.
@ 2019-05-03 8:07 sergiodj+buildbot
2019-05-03 12:17 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-03 8:07 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 661f388860346b3747b3b76479f2a784f3b8e9da ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 661f388860346b3747b3b76479f2a784f3b8e9da
Fix lookup of separate debug file on MS-Windows.
If you put the separate debug file in a global debug directory, GDB on
MS-Windows would fail to find it. This happens because we obtain the
directory to look up the debug file by concatenating the debug
directory name with the leading directories of the executable, and the
latter includes the drive letter on MS-Windows. So we get an invalid
file name like
d:/usr/lib/debug/d:/usr/bin/foo.debug
This commit fixes that by removing the colon of the drive letter,
thus producing
d:/usr/lib/debug/d/usr/bin/foo.debug
gdb/ChangeLog:
2019-05-03 Eli Zaretskii <eliz@gnu.org>
* symfile.c (find_separate_debug_file): Remove colon from the
drive spec of DOS/Windows file names of the target, so that the
file name produced from DEBUGDIR and the target's directory will
be valid on DOS/Windows systems.
gdb/doc/ChangeLog:
2019-05-03 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Separate Debug Files): Document how the
subdirectory of the global debug directory is computed on
MS-Windows/MS-DOS.
(cherry picked from commit 5f2459c233faebe8f882e556b2f4a86594a51292)
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-05-03 8:07 [binutils-gdb/gdb-8.3-branch] Fix lookup of separate debug file on MS-Windows sergiodj+buildbot
@ 2019-05-03 12:17 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-03 12:17 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/8021>
Commit(s) tested:
661f388860346b3747b3b76479f2a784f3b8e9da
Author(s) (in the same order as the commits):
Eli Zaretskii <eliz@gnu.org>
Subject:
Fix lookup of separate debug file on MS-Windows.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/66/661f388860346b3747b3b76479f2a784f3b8e9da/>
*** Diff to previous build ***
============================
PASS -> UNRESOLVED: gdb.dwarf2/multidictionary.exp: GDB is alive
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=13: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=14: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=15: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=16: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=17: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=2: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=3: wait for stops
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=1: inferior 1 exited
PASS -> FAIL: gdb.threads/thread-unwindonsignal.exp: continue until exit
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Treat the .gnu.debuglink and .gnu.debugaltlink sections as debug sections when reading them in from COFF/PE format files.
@ 2019-05-03 7:23 sergiodj+buildbot
2019-05-03 8:07 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-03 7:23 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 35f7673945a9c30fca33d981afdcd42f6fd73a6b ***
Author: Nick Clifton <nickc@redhat.com>
Branch: gdb-8.3-branch
Commit: 35f7673945a9c30fca33d981afdcd42f6fd73a6b
Treat the .gnu.debuglink and .gnu.debugaltlink sections as debug sections when reading them in from COFF/PE format files.
PR 24493
* coffcode.h (styp_to_sec_flags): Treat .gnu.debuglink and
.gnu.debugaltlink sections as debugging sections.
(cherry picked from commit 2cdc1a970d3249888524d251abfb87a9bdc77434)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] (Windows) fix thr != nullptr assert failure in delete_thread_1
@ 2019-04-30 21:20 sergiodj+buildbot
2019-05-01 12:02 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-04-30 21:20 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 002aae07299a446d7ef100410bc603c05d91d152 ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: 002aae07299a446d7ef100410bc603c05d91d152
(Windows) fix thr != nullptr assert failure in delete_thread_1
We have observed that GDB would randomly trip the following
assertion failure when debugging on Windows. When allowing
the program to run until the inferior exits, we occasionally see:
(gdb) cont
Continuing.
[Thread 48192.0xd100 exited with code 1]
[Thread 48192.0x10ad8 exited with code 1]
[Thread 48192.0x36e28 exited with code 0]
[Thread 48192.0x52be4 exited with code 0]
[Thread 48192.0x5aa40 exited with code 0]
../../src/gdb/thread.c:453: internal-error: void delete_thread_1(thread_inf
o*, bool): Assertion `thr != nullptr' failed.
Running the same scenario with some additional traces enabled...
(gdb) set verbose
(gdb) set debugevents
... allows us to understand what the issue is. To understand, we need
to first look at the events received when starting the program, and
in particular which threads got created how. First, we get a
CREATE_PROCESS_DEBUG_EVENT for tid=0x442a8:
gdb: kernel event for pid=317536 tid=0x442a8 code=CREATE_PROCESS_DEBUG_EVENT)
Shortly after, we get some CREATE_THREAD_DEBUG_EVENT events,
one of them being for tid=0x4010c:
gdb: kernel event for pid=317536 tid=0x4010c code=CREATE_THREAD_DEBUG_EVENT)
Fast forward a bit of debugging, and we do a "cont" as above,
at which point the programs reaches the end, and the system reports
"exit" events. The first interesting one is the following:
gdb: kernel event for pid=317536 tid=0x442a8 code=EXIT_THREAD_DEBUG_EVENT)
This is reporting a thread-exit event for a thread whose tid
is the TID of what we call the "main thread". That's the thread
that was created when we received the CREATE_PROCESS_DEBUG_EVENT
notification, and whose TID is actually stored in a global variable
named main_thread_id. This is not something we expected, as
the assumption we made was that the main thread would exit last,
and we would be notified of it via an EXIT_PROCESS_DEBUG_EVENT.
But apparently, this is not always true, at least on Windows Server
2012 and 2016 where this issue has been observed happening randomly.
The consequence of the above notification is that we call
windows_delete_thread for that thread, which removes it from
our list of known threads.
And a little bit later, then we then get the EXIT_PROCESS_DEBUG_EVENT,
and we can see that the associated tid is not the main_thread_id,
but rather the tid of one of the threads that was created during
the lifetime of the program, in this case tid=0x4010c:
gdb: kernel event for pid=317536 tid=0x4010c code=EXIT_PROCESS_DEBUG_EVENT)
And the debug trace printed right after shows why we're crashing:
[Deleting Thread 317536.0x442a8]
We are trying to delete the thread whose tid=0x442a8, which is
the main_thread_id! As we have already deleted that thread before,
the search for it returns a nullptr, which then trips the assertion
check in delete_thread_1.
This commit fixes this issue. It ignores the open question of
what to do with the main_thread_id global, particularly after
that thread has been removed from our list of threads. This will
be dealt with as a separate patch, to allow cherry-picking
this patch into a release branch.
For now, we fix the code so as to avoid this crash.
gdb/ChangeLog:
* windows-nat.c (get_windows_debug_event) <EXIT_PROCESS_DEBUG_EVENT>:
Use current_event.dwThreadId instead of main_thread_id.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-04-30 21:20 [binutils-gdb/gdb-8.3-branch] (Windows) fix thr != nullptr assert failure in delete_thread_1 sergiodj+buildbot
@ 2019-05-01 12:02 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-05-01 12:02 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/8006>
Commit(s) tested:
002aae07299a446d7ef100410bc603c05d91d152
Author(s) (in the same order as the commits):
Joel Brobecker <brobecker@adacore.com>
Subject:
(Windows) fix thr != nullptr assert failure in delete_thread_1
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/00/002aae07299a446d7ef100410bc603c05d91d152/>
*** Diff to previous build ***
============================
PASS -> UNRESOLVED: gdb.dwarf2/multidictionary.exp: GDB is alive
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=10: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=12: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=13: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=14: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=15: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=16: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=18: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=19: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=1: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=3: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=6: wait for stops
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix crash in dwarf2read.c with template parameters
@ 2019-04-30 14:56 sergiodj+buildbot
2019-05-01 6:08 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-04-30 14:56 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 578f1223be227123fc2301ca11f7dcfa01bb2a9d ***
Author: Tom Tromey <tromey@adacore.com>
Branch: gdb-8.3-branch
Commit: 578f1223be227123fc2301ca11f7dcfa01bb2a9d
Fix crash in dwarf2read.c with template parameters
PR c++/24470 concerns a crash in dwarf2read.c that occurs with a
particular test case.
The issue turns out to be that process_structure_scope will pass NULL
to symbol_symtab. This happens because new_symbol decided not to
create a symbol for the particular DIE.
This patch fixes the problem by finding another reasonably-appropriate
symtab to use instead; issuing a complaint if one cannot be found for
some reason.
As mentioned in the bug, I think there are other bugs here. For
example, when using "ptype" on the "l" object in the test case, I
think I would expect to see the template parameter. I didn't research
this too closely, since it seemed more important to fix the crash.
Tested on x86-64 Fedora 29.
I'd like to check this in to the 8.3 branch as well.
gdb/ChangeLog
2019-04-30 Tom Tromey <tromey@adacore.com>
PR c++/24470:
* dwarf2read.c (process_structure_scope): Handle case where type
has template parameters but no symbol was created.
gdb/testsuite/ChangeLog
2019-04-30 Tom Tromey <tromey@adacore.com>
PR c++/24470:
* gdb.cp/temargs.cc: Add test code from PR.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] gdb/configure.ac: add --enable-source-highlight
@ 2019-04-20 16:55 sergiodj+buildbot
2019-04-21 7:49 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-04-20 16:55 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 4ae3a64b95432b580f98d457a2346003877f48d1 ***
Author: Sergei Trofimovich <siarheit@google.com>
Branch: gdb-8.3-branch
Commit: 4ae3a64b95432b580f98d457a2346003877f48d1
gdb/configure.ac: add --enable-source-highlight
Allow disabling source-highlight dependency autodetection even
it exists in the system. More details on problem of automatic
dependencies:
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Automagic_dependencies
Noticed by Jeroen Roovers in https://bugs.gentoo.org/680238
* configure.ac: add --enable-source-highlight switch.
* configure: Regenerate.
* top.c (print_gdb_version): plumb --enable-source-highlight
status to "show configuration".
gdb/ChangeLog
2019-04-19 Sergei Trofimovich <siarheit@google.com>
* configure.ac: add --enable-source-highlight switch.
* configure: Regenerate.
* top.c (print_gdb_version): plumb --enable-source-highlight
status to "show configuration".
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix "list" when control characters are seen
@ 2019-04-20 16:08 sergiodj+buildbot
2019-04-21 1:31 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-04-20 16:08 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 014bc49bfcf15d53c65d956ed337ab3217431483 ***
Author: Tom Tromey <tromey@adacore.com>
Branch: gdb-8.3-branch
Commit: 014bc49bfcf15d53c65d956ed337ab3217431483
Fix "list" when control characters are seen
PR symtab/24423 points out that control characters in a source file
cause a hang in the "list" command, a regression introduced by the
styling changes.
This patch, from the PR, fixes the bug. I've included a minimal
change to the "list" test that exercises this code.
I recall that this bug was discussed on gdb-patches, and I thought
there was a patch there as well, but I was unable to find it.
2019-04-19 Ilya Yu. Malakhov <malakhov@mcst.ru>
PR symtab/24423:
* source.c (print_source_lines_base): Advance "iter" when a
control character is seen.
gdb/testsuite/ChangeLog
2019-04-19 Tom Tromey <tromey@adacore.com>
PR symtab/24423:
* gdb.base/list0.h (foo): Add a control-l character.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-04-20 16:08 [binutils-gdb/gdb-8.3-branch] Fix "list" when control characters are seen sergiodj+buildbot
@ 2019-04-21 1:31 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-04-21 1:31 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7901>
Commit(s) tested:
014bc49bfcf15d53c65d956ed337ab3217431483
Author(s) (in the same order as the commits):
Tom Tromey <tromey@adacore.com>
Subject:
Fix "list" when control characters are seen
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/01/014bc49bfcf15d53c65d956ed337ab3217431483/>
*** Diff to previous build ***
============================
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=11: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=14: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=15: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=16: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=17: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=18: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=19: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=2: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=8: wait for stops
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=1: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix GDB 8.3 regression crash when registers cannot be modified.
@ 2019-04-20 15:20 sergiodj+buildbot
2019-04-20 20:07 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-04-20 15:20 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT bf9a7cea9c88de232f07151614562f81b52630a0 ***
Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: gdb-8.3-branch
Commit: bf9a7cea9c88de232f07151614562f81b52630a0
Fix GDB 8.3 regression crash when registers cannot be modified.
This crash was detected when using GDB with the valgrind gdbserver.
To reproduce:
valgrind sleep 10000
In another window:
gdb
target remote | vgdb
p printf("make sleep print something\n")
=>
terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR'
Aborted
The problem is that the valgrind gdbserver does not allow to change
registers when the inferior is blocked in a system call.
GDB then raises an exception. The exception causes the destructor
of
typedef std::unique_ptr<infcall_suspend_state, infcall_suspend_state_deleter>
infcall_suspend_state_up;
to be called. This destructor itself tries to restore the value of
the registers, and fails similarly. We must catch the exception in
the destructor to avoid crashing GDB.
If the destructor encounters a problem, no warning is produced if
there is an uncaught exception, as in this case, the user will already
be informed of a problem via this exception.
With this change, no crash anymore, and all the valgrind 3.15 tests
pass succesfully.
Note: when this patch is approved, I will push an equivalent patch
on master, but with TRY/CATCH/e.message () replaced by
try/catch/e.what ().
gdb/ChangeLog
2019-04-19 Philippe Waroquiers <philippe.waroquiers@skynet.be>
* inferior.h (struct infcall_suspend_state_deleter):
Catch exception in destructor to avoid crash.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Another fix for GDB styling
@ 2019-04-12 13:08 sergiodj+buildbot
2019-04-14 16:08 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-04-12 13:08 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT cd3c4bccf4684fd30d125ecd27146c79e5087b02 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: cd3c4bccf4684fd30d125ecd27146c79e5087b02
Another fix for GDB styling
gdb/ChangeLog:
2019-04-12 Eli Zaretskii <eliz@gnu.org>
* utils.c (prompt_for_continue): Don't restore the styling at the
end, as applied_style has the wrong value. This fixes styling in
long lists of file names that are interrupted by the "Continue?"
prompt.
(cherry picked from commit 51196bbc5618a3741bd7bbed01ac76b25a2e6f9c)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix testsuite hangs when gdb_test_multiple body errors out
@ 2019-03-28 18:47 sergiodj+buildbot
2019-03-29 6:43 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-28 18:47 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 7f45a45af30f6988472ea8f954f94713c45ad478 ***
Author: Pedro Alves <palves@redhat.com>
Branch: gdb-8.3-branch
Commit: 7f45a45af30f6988472ea8f954f94713c45ad478
Fix testsuite hangs when gdb_test_multiple body errors out
This commit fixes a regression in the testsuite itself, triggered by
errors being raised from within gdb_test_multiple, originally reported
by Pedro Franco de Carvalho's at
<https://sourceware.org/ml/gdb-patches/2019-03/msg00160.html>. Parts
of the commit message are based on his report.
This started happening due to a commit that was introduced recently,
and it can cause the testsuite to hang.
The commit that triggers this is:
fe1a5cad302b5535030cdf62895e79512713d738
[gdb/testsuite] Log wait status on process no longer exists error
That commit introduces a new "eof" block in gdb_test_multiple. That
is not incorrect itself, but dejagnu's remote_expect is picking that
block as the "default" action when an error is raised from within the
commands inside a call to gdb_test_multiple:
# remote_expect works basically the same as standard expect, but it
# also takes care of getting the file descriptor from the specified
# host and also calling the timeout/eof/default section if there is an
# error on the expect call.
#
proc remote_expect { board timeout args } {
I find that "feature" surprising, and I don't really know why it
exists, but this means that the eof section that remote_expect picks
as the error block can be executed even when there was no actual eof
and the GDB process is still running, so the wait introduced in the
commit that tries to get the exit status of GDB hangs forever, while
GDB itself waits for input.
This only happens when there are internal testsuite errors (not
testcase failures). This can be reproduced easily with a testcase
such as:
gdb_start
gdb_test_multiple "show version" "show version" {
-re ".*" {
error "forced error"
}
}
I think that working around this in GDB is useful so that the
testsuite doesn't hang in these cases.
Adding an empty "default" block at the end of the expect body in
gdb_test_multiple doesn't work, because dejagnu gives preference to
"eof" blocks:
if { $x eq "eof" } {
set save_next 1
} elseif { $x eq "default" || $x eq "timeout" } {
if { $error_sect eq "" } {
set save_next 1
}
}
And we do have "eof" blocks. So we need to make sure that the last
"eof" block is safe to use as the default error block. It's also
pedantically incorrect to print
"ERROR: Process no longer exists"
which is what we'd get if the last eof block we have was selected
(more below on this).
So this commit solves this by appending an "eof" with an empty
spawn_id list, so that it won't ever match.
Now, why is the first "eof" block selected today as the error block,
instead of the last one?
The reason is that remote_expect, while parsing the body to select the
default block to execute after an error, is affected by the comments
in the body (since they are also parsed).
If this comment in gdb_test_multiple
# patterns below apply to any spawn id specified.
is changed to
# The patterns below apply to any spawn id specified.
then the second eof block is selected and there is no hang.
Any comment at that same place with an even number of tokens also
works.
This is IMO a coincidence caused by how comments work in TCL.
Comments should only appear in places where a command can appear. And
here, remote_expect is parsing a list of options, not commands, so
it's not unreasonable to not parse comments, similarly to how this:
set a_list {
an_element
# another_element
}
results in a list with three elements, not one element.
The fact that comments with an even number of tokens work is just a
coincidence of how remote_expect's little state machine is
implemented.
I thought we could solve this by stripping out comment lines in
gdb_expect, but I didn't find an easy way to do that. Particularly, a
couple naive approaches I tried run into complications. For example,
we have gdb_test calls with regular expressions that include sequences
like "\r\n#", and by the time we get to gdb_expect, the \r\n have
already been expanded to a real newline, so just splitting the whole
body at newline boundaries, looking for lines that start with #
results in incorrectly stripping out half of the gdb_text regexp. I
think it's better (at least in this commit), to move the comments out
of the list, because it's much simpler and risk free.
gdb/testsuite/ChangeLog:
2019-03-25 Pedro Alves <palves@redhat.com>
* lib/gdb.exp (gdb_test_multiple): Split appends to $code and
move comments outside list. Append '-i "" eof' section.
(cherry picked from commit 9a93502fa81734d39f213ccb33b497bc40e1423d)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Bump GDB version number to 8.2.91.DATE-git.
@ 2019-03-27 1:03 sergiodj+buildbot
2019-03-27 18:56 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-27 1:03 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT d18988f72bffbd08e345dc18c3dd2317157cab1a ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: d18988f72bffbd08e345dc18c3dd2317157cab1a
Bump GDB version number to 8.2.91.DATE-git.
gdb/ChangeLog:
* version.in: Set GDB version number to 8.2.91.DATE-git.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Set GDB version number to 8.2.91.
@ 2019-03-27 0:32 sergiodj+buildbot
2019-03-27 16:01 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-27 0:32 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT d49ac41ec62576de1a3d2038fe99375c120ef5ef ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: d49ac41ec62576de1a3d2038fe99375c120ef5ef
Set GDB version number to 8.2.91.
gdb/ChangeLog:
* version.in: Set GDB version number to 8.2.91.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-27 0:32 [binutils-gdb/gdb-8.3-branch] Set GDB version number to 8.2.91 sergiodj+buildbot
@ 2019-03-27 16:01 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-27 16:01 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7735>
Commit(s) tested:
d49ac41ec62576de1a3d2038fe99375c120ef5ef
Author(s) (in the same order as the commits):
Joel Brobecker <brobecker@adacore.com>
Subject:
Set GDB version number to 8.2.91.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/d4/d49ac41ec62576de1a3d2038fe99375c120ef5ef/>
*** Diff to previous build ***
============================
new FAIL: gdb.base/break-idempotent.exp: always-inserted on: hbreak: can't run to main
new FAIL: gdb.base/break-idempotent.exp: always-inserted on: watch: info breakpoints
PASS -> UNRESOLVED: gdb.base/break-idempotent.exp: always-inserted on: watch: set breakpoint always-inserted on
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=12: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=13: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=5: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=8: wait for stops
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
PASS -> FAIL: gdb.trace/mi-tsv-changed.exp: create delete modify: tvariable $tvar3 modified
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] gdb/testsuite: Prepare for DejaGnu 1.6.2
@ 2019-03-26 23:59 sergiodj+buildbot
2019-03-27 14:35 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-26 23:59 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 8a9d17eafbc2b2db8b3dc3ba5ead06237176eb87 ***
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: gdb-8.3-branch
Commit: 8a9d17eafbc2b2db8b3dc3ba5ead06237176eb87
gdb/testsuite: Prepare for DejaGnu 1.6.2
Changes in DejaGnu 1.6.2 mean that our testsuite will no longer run.
This is because of some confusion over how the gdb.exp file is
handled.
The gdb.exp file is really the tool init file, which is loaded from
within the DejaGnu core, and it should not be loaded directly from any
other file in the testsuite.
DejaGnu tries to prevent the same library being loaded twice by
remembering the names of library files as they are loaded. Until
recently loading the tool init file in DejaGnu was very similar to
loading a library file, as a result, loading the gdb.exp tool init
file simply recorded 'gdb.exp' as having been loaded, future attempts
to load 'gdb.exp' as a library would then be ignored (as the file was
marked as already loaded).
DejaGnu has now changed so that it supports having both a tool init
file and a library with the same name, something that was not possible
before. What this means however is that when the core loads the
'gdb.exp' tool init file it no longer marks the library 'gdb.exp' as
having been loaded. When we then execute 'load_lib gdb.exp' we then
try to reload the 'gdb.exp' file.
Unfortunately our gdb.exp file can only be loaded once. It use of
'rename cd builtin_cd' means that a second attempt to load this file
will fail.
This was discussed on the DejaGnu list here:
http://lists.gnu.org/archive/html/dejagnu/2019-03/msg00000.html
and the suggested advice is that, unless we have some real requirement
to load the tool init file twice, we should remove calls to 'load_lib
gdb.exp' and rely on DejaGnu to load the file for us, which is what
this patch does.
I've tested with native X86-64/GNU Linux and see no regressions.
gdb/testsuite/ChangeLog:
* config/default.exp: Remove 'load_lib gdb.exp'.
* config/monitor.exp: Likewise.
* config/sid.exp: Likewise.
* config/sim.exp: Likewise.
* config/slite.exp: Likewise.
* config/unix.exp: Likewise.
* gdb.base/default.exp: Remove unhelpful comment.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Merge handle_inferior_event and handle_inferior_event_1
@ 2019-03-26 22:00 sergiodj+buildbot
2019-03-27 9:47 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-26 22:00 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT e8ad6586f1568233cbd48d041656d0774ffdc0fb ***
Author: Tom Tromey <tromey@adacore.com>
Branch: gdb-8.3-branch
Commit: e8ad6586f1568233cbd48d041656d0774ffdc0fb
Merge handle_inferior_event and handle_inferior_event_1
I noticed that handle_inferior_event is just a small wrapper that
frees the value chain. This patch replaces it with a
scoped_value_mark, reducing the number of lines of code here.
Regression tested on x86-64 Fedora 29.
gdb/ChangeLog
2019-03-20 Tom Tromey <tromey@adacore.com>
PR gdb/24391
* infrun.c (handle_inferior_event): Rename from
handle_inferior_event_1. Create a scoped_value_mark.
(handle_inferior_event): Remove.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-26 22:00 [binutils-gdb/gdb-8.3-branch] Merge handle_inferior_event and handle_inferior_event_1 sergiodj+buildbot
@ 2019-03-27 9:47 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-27 9:47 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7732>
Commit(s) tested:
e8ad6586f1568233cbd48d041656d0774ffdc0fb
Author(s) (in the same order as the commits):
Tom Tromey <tromey@adacore.com>
Subject:
Merge handle_inferior_event and handle_inferior_event_1
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/e8/e8ad6586f1568233cbd48d041656d0774ffdc0fb/>
*** Diff to previous build ***
============================
PASS -> UNRESOLVED: gdb.dwarf2/multidictionary.exp: GDB is alive
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=11: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=12: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=4: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=5: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=6: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=8: wait for stops
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: detach: continue
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix use-after-free in source_cache::get_source_lines
@ 2019-03-26 1:15 sergiodj+buildbot
2019-03-26 12:00 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-26 1:15 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 154eab6dec772e705b4eefe34ebfefec8808c2cf ***
Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: gdb-8.3-branch
Commit: 154eab6dec772e705b4eefe34ebfefec8808c2cf
Fix use-after-free in source_cache::get_source_lines
Commit ab42892fb7d2 ("Fix vertical scrolling of TUI source window")
introduced a use-after-free in source_cache::get_source_lines.
At the beginning of the method, we get the fullname of the symtab:
const char *fullname = symtab_to_fullname (s);
fullname points to the string owned by the symtab (s.fullname). When we
later do
scoped_fd desc = open_source_file (s);
s.fullname gets reallocated (even though the string contents may not
change). The fullname local variable now points to freed memory.
To avoid it, refresh the value of fullname after calling
open_source_file.
Here is the ASan report:
$ ./gdb -nx --data-directory=data-directory ./a.out
(gdb) start
Temporary breakpoint 1 at 0x1130: file test.cpp, line 12.
Starting program: /home/simark/build/binutils-gdb/gdb/a.out
Temporary breakpoint 1, main () at test.cpp:12
=================================================================
==26068==ERROR: AddressSanitizer: heap-use-after-free on address 0x6210003d4100 at pc 0x7fed89a34681 bp 0x7ffd8d185d80 sp 0x7ffd8d185528
READ of size 2 at 0x6210003d4100 thread T0
#0 0x7fed89a34680 in __interceptor_strlen /build/gcc/src/gcc/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:301
#1 0x55b6edf6c2f7 in std::char_traits<char>::length(char const*) /usr/include/c++/8.2.1/bits/char_traits.h:320
#2 0x55b6edf6c9b2 in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(char const*, std::allocator<char> const&) /usr/include/c++/8.2.1/bits/basic_string.h:516
#3 0x55b6ef09121b in source_cache::get_source_lines(symtab*, int, int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*) /home/simark/src/binutils-gdb/gdb/source-cache.c:214
#4 0x55b6ef0a15cb in print_source_lines_base /home/simark/src/binutils-gdb/gdb/source.c:1340
#5 0x55b6ef0a2045 in print_source_lines(symtab*, int, int, enum_flags<print_source_lines_flag>) /home/simark/src/binutils-gdb/gdb/source.c:1415
#6 0x55b6ef112c87 in print_frame_info(frame_info*, int, print_what, int, int) /home/simark/src/binutils-gdb/gdb/stack.c:914
#7 0x55b6ef10e90d in print_stack_frame(frame_info*, int, print_what, int) /home/simark/src/binutils-gdb/gdb/stack.c:180
#8 0x55b6ee9592f8 in print_stop_location /home/simark/src/binutils-gdb/gdb/infrun.c:7853
#9 0x55b6ee95948f in print_stop_event(ui_out*) /home/simark/src/binutils-gdb/gdb/infrun.c:7870
#10 0x55b6ef34b962 in tui_on_normal_stop /home/simark/src/binutils-gdb/gdb/tui/tui-interp.c:98
#11 0x55b6ee01a14d in std::_Function_handler<void (bpstats*, int), void (*)(bpstats*, int)>::_M_invoke(std::_Any_data const&, bpstats*&&, int&&) /usr/include/c++/8.2.1/bits/std_function.h:297
#12 0x55b6ee965415 in std::function<void (bpstats*, int)>::operator()(bpstats*, int) const /usr/include/c++/8.2.1/bits/std_function.h:687
#13 0x55b6ee962f1b in gdb::observers::observable<bpstats*, int>::notify(bpstats*, int) const /home/simark/src/binutils-gdb/gdb/common/observable.h:106
#14 0x55b6ee95a6e7 in normal_stop() /home/simark/src/binutils-gdb/gdb/infrun.c:8142
#15 0x55b6ee93f236 in fetch_inferior_event(void*) /home/simark/src/binutils-gdb/gdb/infrun.c:3782
#16 0x55b6ee8f2641 in inferior_event_handler(inferior_event_type, void*) /home/simark/src/binutils-gdb/gdb/inf-loop.c:43
#17 0x55b6eea2a1f0 in handle_target_event /home/simark/src/binutils-gdb/gdb/linux-nat.c:4358
#18 0x55b6ee7045f1 in handle_file_event /home/simark/src/binutils-gdb/gdb/event-loop.c:733
#19 0x55b6ee704e89 in gdb_wait_for_event /home/simark/src/binutils-gdb/gdb/event-loop.c:859
#20 0x55b6ee7027b5 in gdb_do_one_event() /home/simark/src/binutils-gdb/gdb/event-loop.c:322
#21 0x55b6ee702907 in start_event_loop() /home/simark/src/binutils-gdb/gdb/event-loop.c:371
#22 0x55b6eeadfc16 in captured_command_loop /home/simark/src/binutils-gdb/gdb/main.c:331
#23 0x55b6eeae2ef9 in captured_main /home/simark/src/binutils-gdb/gdb/main.c:1174
#24 0x55b6eeae30c2 in gdb_main(captured_main_args*) /home/simark/src/binutils-gdb/gdb/main.c:1190
#25 0x55b6edf4fa89 in main /home/simark/src/binutils-gdb/gdb/gdb.c:32
#26 0x7fed88ad8222 in __libc_start_main (/usr/lib/libc.so.6+0x24222)
#27 0x55b6edf4f86d in _start (/home/simark/build/binutils-gdb/gdb/gdb+0x197186d)
0x6210003d4100 is located 0 bytes inside of 4096-byte region [0x6210003d4100,0x6210003d5100)
freed by thread T0 here:
#0 0x7fed89a8ac19 in __interceptor_free /build/gcc/src/gcc/libsanitizer/asan/asan_malloc_linux.cc:66
#1 0x55b6edfe12df in xfree<char> /home/simark/src/binutils-gdb/gdb/common/common-utils.h:60
#2 0x55b6edfea675 in gdb::xfree_deleter<char>::operator()(char*) const /home/simark/src/binutils-gdb/gdb/common/gdb_unique_ptr.h:34
#3 0x55b6edfe532c in std::unique_ptr<char, gdb::xfree_deleter<char> >::reset(char*) /usr/include/c++/8.2.1/bits/unique_ptr.h:382
#4 0x55b6edfe7329 in std::unique_ptr<char, gdb::xfree_deleter<char> >::operator=(std::unique_ptr<char, gdb::xfree_deleter<char> >&&) /usr/include/c++/8.2.1/bits/unique_ptr.h:289
#5 0x55b6ef09ec2b in find_and_open_source(char const*, char const*, std::unique_ptr<char, gdb::xfree_deleter<char> >*) /home/simark/src/binutils-gdb/gdb/source.c:990
#6 0x55b6ef09f56a in open_source_file(symtab*) /home/simark/src/binutils-gdb/gdb/source.c:1069
#7 0x55b6ef090f78 in source_cache::get_source_lines(symtab*, int, int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*) /home/simark/src/binutils-gdb/gdb/source-cache.c:205
#8 0x55b6ef0a15cb in print_source_lines_base /home/simark/src/binutils-gdb/gdb/source.c:1340
#9 0x55b6ef0a2045 in print_source_lines(symtab*, int, int, enum_flags<print_source_lines_flag>) /home/simark/src/binutils-gdb/gdb/source.c:1415
#10 0x55b6ef112c87 in print_frame_info(frame_info*, int, print_what, int, int) /home/simark/src/binutils-gdb/gdb/stack.c:914
#11 0x55b6ef10e90d in print_stack_frame(frame_info*, int, print_what, int) /home/simark/src/binutils-gdb/gdb/stack.c:180
#12 0x55b6ee9592f8 in print_stop_location /home/simark/src/binutils-gdb/gdb/infrun.c:7853
#13 0x55b6ee95948f in print_stop_event(ui_out*) /home/simark/src/binutils-gdb/gdb/infrun.c:7870
#14 0x55b6ef34b962 in tui_on_normal_stop /home/simark/src/binutils-gdb/gdb/tui/tui-interp.c:98
#15 0x55b6ee01a14d in std::_Function_handler<void (bpstats*, int), void (*)(bpstats*, int)>::_M_invoke(std::_Any_data const&, bpstats*&&, int&&) /usr/include/c++/8.2.1/bits/std_function.h:297
#16 0x55b6ee965415 in std::function<void (bpstats*, int)>::operator()(bpstats*, int) const /usr/include/c++/8.2.1/bits/std_function.h:687
#17 0x55b6ee962f1b in gdb::observers::observable<bpstats*, int>::notify(bpstats*, int) const /home/simark/src/binutils-gdb/gdb/common/observable.h:106
#18 0x55b6ee95a6e7 in normal_stop() /home/simark/src/binutils-gdb/gdb/infrun.c:8142
#19 0x55b6ee93f236 in fetch_inferior_event(void*) /home/simark/src/binutils-gdb/gdb/infrun.c:3782
#20 0x55b6ee8f2641 in inferior_event_handler(inferior_event_type, void*) /home/simark/src/binutils-gdb/gdb/inf-loop.c:43
#21 0x55b6eea2a1f0 in handle_target_event /home/simark/src/binutils-gdb/gdb/linux-nat.c:4358
#22 0x55b6ee7045f1 in handle_file_event /home/simark/src/binutils-gdb/gdb/event-loop.c:733
#23 0x55b6ee704e89 in gdb_wait_for_event /home/simark/src/binutils-gdb/gdb/event-loop.c:859
#24 0x55b6ee7027b5 in gdb_do_one_event() /home/simark/src/binutils-gdb/gdb/event-loop.c:322
#25 0x55b6ee702907 in start_event_loop() /home/simark/src/binutils-gdb/gdb/event-loop.c:371
#26 0x55b6eeadfc16 in captured_command_loop /home/simark/src/binutils-gdb/gdb/main.c:331
#27 0x55b6eeae2ef9 in captured_main /home/simark/src/binutils-gdb/gdb/main.c:1174
#28 0x55b6eeae30c2 in gdb_main(captured_main_args*) /home/simark/src/binutils-gdb/gdb/main.c:1190
#29 0x55b6edf4fa89 in main /home/simark/src/binutils-gdb/gdb/gdb.c:32
previously allocated by thread T0 here:
#0 0x7fed89a8b019 in __interceptor_malloc /build/gcc/src/gcc/libsanitizer/asan/asan_malloc_linux.cc:86
#1 0x7fed88af983f in realpath@@GLIBC_2.3 (/usr/lib/libc.so.6+0x4583f)
#2 0x7fed899dbbbc in __interceptor_canonicalize_file_name /build/gcc/src/gcc/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:3297
#3 0x55b6ee376a03 in gdb_realpath(char const*) /home/simark/src/binutils-gdb/gdb/common/pathstuff.c:72
#4 0x55b6ef09ec12 in find_and_open_source(char const*, char const*, std::unique_ptr<char, gdb::xfree_deleter<char> >*) /home/simark/src/binutils-gdb/gdb/source.c:990
#5 0x55b6ef09f56a in open_source_file(symtab*) /home/simark/src/binutils-gdb/gdb/source.c:1069
#6 0x55b6ef0a0f12 in print_source_lines_base /home/simark/src/binutils-gdb/gdb/source.c:1270
#7 0x55b6ef0a2045 in print_source_lines(symtab*, int, int, enum_flags<print_source_lines_flag>) /home/simark/src/binutils-gdb/gdb/source.c:1415
#8 0x55b6ef112c87 in print_frame_info(frame_info*, int, print_what, int, int) /home/simark/src/binutils-gdb/gdb/stack.c:914
#9 0x55b6ef10e90d in print_stack_frame(frame_info*, int, print_what, int) /home/simark/src/binutils-gdb/gdb/stack.c:180
#10 0x55b6ee9592f8 in print_stop_location /home/simark/src/binutils-gdb/gdb/infrun.c:7853
#11 0x55b6ee95948f in print_stop_event(ui_out*) /home/simark/src/binutils-gdb/gdb/infrun.c:7870
#12 0x55b6ef34b962 in tui_on_normal_stop /home/simark/src/binutils-gdb/gdb/tui/tui-interp.c:98
#13 0x55b6ee01a14d in std::_Function_handler<void (bpstats*, int), void (*)(bpstats*, int)>::_M_invoke(std::_Any_data const&, bpstats*&&, int&&) /usr/include/c++/8.2.1/bits/std_function.h:297
#14 0x55b6ee965415 in std::function<void (bpstats*, int)>::operator()(bpstats*, int) const /usr/include/c++/8.2.1/bits/std_function.h:687
#15 0x55b6ee962f1b in gdb::observers::observable<bpstats*, int>::notify(bpstats*, int) const /home/simark/src/binutils-gdb/gdb/common/observable.h:106
#16 0x55b6ee95a6e7 in normal_stop() /home/simark/src/binutils-gdb/gdb/infrun.c:8142
#17 0x55b6ee93f236 in fetch_inferior_event(void*) /home/simark/src/binutils-gdb/gdb/infrun.c:3782
#18 0x55b6ee8f2641 in inferior_event_handler(inferior_event_type, void*) /home/simark/src/binutils-gdb/gdb/inf-loop.c:43
#19 0x55b6eea2a1f0 in handle_target_event /home/simark/src/binutils-gdb/gdb/linux-nat.c:4358
#20 0x55b6ee7045f1 in handle_file_event /home/simark/src/binutils-gdb/gdb/event-loop.c:733
#21 0x55b6ee704e89 in gdb_wait_for_event /home/simark/src/binutils-gdb/gdb/event-loop.c:859
#22 0x55b6ee7027b5 in gdb_do_one_event() /home/simark/src/binutils-gdb/gdb/event-loop.c:322
#23 0x55b6ee702907 in start_event_loop() /home/simark/src/binutils-gdb/gdb/event-loop.c:371
#24 0x55b6eeadfc16 in captured_command_loop /home/simark/src/binutils-gdb/gdb/main.c:331
#25 0x55b6eeae2ef9 in captured_main /home/simark/src/binutils-gdb/gdb/main.c:1174
#26 0x55b6eeae30c2 in gdb_main(captured_main_args*) /home/simark/src/binutils-gdb/gdb/main.c:1190
#27 0x55b6edf4fa89 in main /home/simark/src/binutils-gdb/gdb/gdb.c:32
#28 0x7fed88ad8222 in __libc_start_main (/usr/lib/libc.so.6+0x24222)
gdb/ChangeLog:
* source-cache.c (source_cache::get_source_lines): Re-read
fullname after calling open_source_file.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix first time you type UP or DOWN in TUI's command window
@ 2019-03-18 19:27 sergiodj+buildbot
2019-03-19 6:12 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 19:27 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 7fa34358ef888d242c3441b2a2342297b17775e3 ***
Author: Pedro Alves <palves@redhat.com>
Branch: gdb-8.3-branch
Commit: 7fa34358ef888d242c3441b2a2342297b17775e3
Fix first time you type UP or DOWN in TUI's command window
The first time you type UP or DOWN arrow in the command window, GDB
should scroll the source window, but instead it displays the line
number and the file name in the command window(?).
What happens there is that the first time we call
tui_ui_out::do_field_int, it doesn't initialize m_line, because
m_start_of_line is -1, as set by the constructor; and then the
following call to tui_ui_out::do_field_string falls back to
cli_ui_out::do_field_string because m_line is zero.
The problem is caused by a typo in the C++ification of tui_ui_out,
commit 112e8700a6f, where m_line and m_start_of_line's initial values
were swapped from what they used to be:
-struct ui_out *
-tui_out_new (struct ui_file *stream)
+tui_ui_out::tui_ui_out (ui_file *stream)
+: cli_ui_out (stream, 0),
+ m_line (0),
+ m_start_of_line (-1)
{
-
- /* Initialize our fields. */
- data->line = -1;
- data->start_of_line = 0;
This commit fixes it.
gdb/ChangeLog:
2019-03-18 Pedro Alves <palves@redhat.com>
Eli Zaretskii <eliz@gnu.org>
* tui/tui-out.c (tui_ui_out::tui_ui_out): Fix initialization of
m_line and m_start_of_line.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix gdb/TUI behavior in response to [Enter] keypress
@ 2019-03-18 18:37 sergiodj+buildbot
2019-03-19 2:56 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 18:37 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 2e73c81b875328f60d22d74ddb8dbe77757d9737 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 2e73c81b875328f60d22d74ddb8dbe77757d9737
Fix gdb/TUI behavior in response to [Enter] keypress
gdb/ChangeLog:
2019-03-18 Eli Zaretskii <eliz@gnu.org>
* tui/tui-io.c (gdb_wgetch): Don't echo CR.
(tui_getc): When gdb_wgetch returns a CR, behave the same as when
it returns a newline. This fixes a regression in TUI mode, whereby
the next line is output on the same screen line as the user input.
(cherry picked from commit b17c4cd078e2d1d8951951016815e474fb133780)
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-18 18:37 [binutils-gdb/gdb-8.3-branch] Fix gdb/TUI behavior in response to [Enter] keypress sergiodj+buildbot
@ 2019-03-19 2:56 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-19 2:56 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7680>
Commit(s) tested:
2e73c81b875328f60d22d74ddb8dbe77757d9737
Author(s) (in the same order as the commits):
Eli Zaretskii <eliz@gnu.org>
Subject:
Fix gdb/TUI behavior in response to [Enter] keypress
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/2e/2e73c81b875328f60d22d74ddb8dbe77757d9737/>
*** Diff to previous build ***
============================
PASS -> UNRESOLVED: gdb.dwarf2/multidictionary.exp: GDB is alive
new FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=kill: can't run to child_function
new FAIL: gdb.python/py-rbreak.exp: can't run to main
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=10: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=15: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=16: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=2: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=4: wait for stops
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=0: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Improve/fix the TUI's current source line highlight
@ 2019-03-18 15:25 sergiodj+buildbot
2019-03-18 21:58 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 15:25 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 77b66be9699f4800e169acb5cba6c96bd9cb327b ***
Author: Pedro Alves <palves@redhat.com>
Branch: gdb-8.3-branch
Commit: 77b66be9699f4800e169acb5cba6c96bd9cb327b
Improve/fix the TUI's current source line highlight
With styling enabled, I think the way we display the TUI's
highlighted/current line is very ugly and distracting. The problem in
my view is that we reverse foreground/background in colored text as
well, leading to rainbow of background colors.
This patch changes that to something that I find much more sensible --
only reverse the default foreground/background colors, leave styled
text colors alone. If the foreground color is not the default
(because the text was styled), leave the foreground color as is. If
e.g., the terminal is fg=BLACK, and bg=WHITE, and the style wants to
print text in RED, reverse the background color (print in BLACK), but
still print the text in RED.
Note: The new ui_file_style::set_fg method isn't called set_foreground
instead, because set_foreground is a macro in /usr/lib/term.h (ncurses).
gdb/ChangeLog:
2019-03-18 Pedro Alves <palves@redhat.com>
* tui/tui-io.c (reverse_mode_p, reverse_save_bg, reverse_save_fg):
New globals.
(apply_style): New, factored out from ...
(apply_ansi_escape): ... this. Handle reverse video mode.
(tui_set_reverse_mode): New function.
* tui/tui-io.h (tui_set_reverse_mode): New declaration.
* tui/tui-winsource.c (tui_show_source_line): Use
tui_set_reverse_mode instead of setting A_STANDOUT.
* ui-style.h (struct ui_file_style) <set_reverse, set_fg, set_bg>:
New setter methods.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-18 15:25 [binutils-gdb/gdb-8.3-branch] Improve/fix the TUI's current source line highlight sergiodj+buildbot
@ 2019-03-18 21:58 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-18 21:58 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7677>
Commit(s) tested:
77b66be9699f4800e169acb5cba6c96bd9cb327b
Author(s) (in the same order as the commits):
Pedro Alves <palves@redhat.com>
Subject:
Improve/fix the TUI's current source line highlight
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/77/77b66be9699f4800e169acb5cba6c96bd9cb327b/>
*** Diff to previous build ***
============================
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=11: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=14: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=17: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=19: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=8: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=9: wait for stops
PASS -> FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: detach: continue
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=0: inferior 1 exited
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix redisplay of the current line in GDB TUI mode
@ 2019-03-17 16:32 sergiodj+buildbot
2019-03-17 18:54 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-17 16:32 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 89ab4b06975ffc59c8a70d0cee7608ed26c836ab ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 89ab4b06975ffc59c8a70d0cee7608ed26c836ab
Fix redisplay of the current line in GDB TUI mode
Without this change, when the current line is longer than the source
window width, redisplaying that line overwrites the window frame and
also portions of the next line.
gdb/ChangeLog:
2019-03-17 Eli Zaretskii <eliz@gnu.org>
* tui/tui-winsource.c (tui_set_is_exec_point_at): Call
tui_refill_source_window instead of tui_refresh_win, to update the
current execution line. This fixes redisplay of the current line
when stepping through very long lines with "next" or "step".
(cherry picked from commit f7f0a12390fc514a5b7b38d1b23397d87532ce05)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix vertical scrolling of TUI source window
@ 2019-03-16 18:28 sergiodj+buildbot
2019-03-17 3:31 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-16 18:28 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT ed4c1406c8d0e7dfad6eb0c7ef1c01999f590e2a ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: ed4c1406c8d0e7dfad6eb0c7ef1c01999f590e2a
Fix vertical scrolling of TUI source window
gdb/ChangeLog:
2019-03-16 Eli Zaretskii <eliz@gnu.org>
* source-cache.c (source_cache::get_source_lines): Call
find_source_lines to initialize s->nlines. This fixes vertical
scrolling of TUI source window when the DOWN arrow is pressed.
(cherry picked from commit ab42892fb7d265e72a85e918d4f5c6dfeee3fcd8)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Revert "Use wclrtoeol in tui_show_source_line"
@ 2019-03-16 12:45 sergiodj+buildbot
2019-03-16 22:27 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-16 12:45 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 7b9d48cade45dc370b129f7279c87556af442d68 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 7b9d48cade45dc370b129f7279c87556af442d68
Revert "Use wclrtoeol in tui_show_source_line"
gdb/ChangeLog:
2019-03-16 Eli Zaretskii <eliz@gnu.org>
* tui/tui-winsource.c (tui_show_source_line): Revert "Use
wclrtoeol in tui_show_source_line". This reverts changes made in
commit 4a3045920bbe4e50a0f4920b0fdc4e88ef23015c.
(cherry picked from commit 798e1c302af509c31839c5c3b50c058b61206ee7)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] The NEWS file had two "New targets" sections for 8.3.
@ 2019-03-14 16:38 sergiodj+buildbot
2019-03-15 2:56 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-14 16:38 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT aaa9eae67da575bbb29aa76a13929666aa241da1 ***
Author: John Baldwin <jhb@FreeBSD.org>
Branch: gdb-8.3-branch
Commit: aaa9eae67da575bbb29aa76a13929666aa241da1
The NEWS file had two "New targets" sections for 8.3.
gdb/ChangeLog:
* NEWS: Combine separate "New targets" sections for 8.3.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-14 16:38 [binutils-gdb/gdb-8.3-branch] The NEWS file had two "New targets" sections for 8.3 sergiodj+buildbot
@ 2019-03-15 2:56 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-15 2:56 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7638>
Commit(s) tested:
aaa9eae67da575bbb29aa76a13929666aa241da1
Author(s) (in the same order as the commits):
John Baldwin <jhb@FreeBSD.org>
Subject:
The NEWS file had two "New targets" sections for 8.3.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/aa/aaa9eae67da575bbb29aa76a13929666aa241da1/>
*** Diff to previous build ***
============================
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=10: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=14: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=15: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=16: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=18: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=19: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=2: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=4: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=6: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=8: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=9: wait for stops
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=1: inferior 1 exited
PASS -> FAIL: gdb.threads/thread-unwindonsignal.exp: continue until exit
PASS -> FAIL: gdb.trace/mi-tsv-changed.exp: create delete modify: tvariable $tvar3 modified
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix colors in TUI mode in MS-Windows build with ncurses
@ 2019-03-14 15:49 sergiodj+buildbot
2019-03-14 22:48 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-14 15:49 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 7cf3f4acfddebe44f80b71dcdf1041d870c6d100 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 7cf3f4acfddebe44f80b71dcdf1041d870c6d100
Fix colors in TUI mode in MS-Windows build with ncurses
The MS-Windows port of ncurses fails to switch to a color pair if
one or both of the colors are the implicit default colors. This
change records the default colors when TUI is initialized, and
then specifies them explicitly when a color pair uses the default
colors. This allows color styling in TUI mode on MS-Windows.
gdb/ChangeLog:
2019-03-14 Eli Zaretskii <eliz@gnu.org>
* tui/tui-io.c [__MINGW32__]: Include windows.h. Declare
ncurses_norm_attr.
(tui_initialize_io) [__MINGW32__]: Record the default terminal
colors in ncurses_norm_attr.
(apply_ansi_escape) [__MINGW32__]: If a color in a color pair is
"none", replace it with the default color recorded in
ncurses_norm_attr.
(cherry picked from commit 3fff2c370cd658877be8107bfe9dde8dd0470b46)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Avoid a crash in source_cache::extract_lines
@ 2019-03-14 13:08 sergiodj+buildbot
2019-03-14 19:59 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-14 13:08 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 655aeea04784cdc3e4dfbc0801e7be56f9a1ec11 ***
Author: Tom Tromey <tromey@adacore.com>
Branch: gdb-8.3-branch
Commit: 655aeea04784cdc3e4dfbc0801e7be56f9a1ec11
Avoid a crash in source_cache::extract_lines
If the first requested line is larger than the number of lines in the
source buffer, source_cache::extract_lines could crash, because it
would try to pass string::npos" to string::substr.
This patch avoids the crash by checking for this case.
This version of the patch changes get_source_lines to return
std::string.
2019-03-14 Tom Tromey <tromey@adacore.com>
* source-cache.h (class source_cache) <get_source_lines>: Return
std::string.
* source-cache.c (source_cache::extract_lines): Handle case where
first_pos==npos. Return std::string.
(source_cache::get_source_lines): Update.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-14 13:08 [binutils-gdb/gdb-8.3-branch] Avoid a crash in source_cache::extract_lines sergiodj+buildbot
@ 2019-03-14 19:59 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-14 19:59 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7633>
Commit(s) tested:
655aeea04784cdc3e4dfbc0801e7be56f9a1ec11
Author(s) (in the same order as the commits):
Tom Tromey <tromey@adacore.com>
Subject:
Avoid a crash in source_cache::extract_lines
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/65/655aeea04784cdc3e4dfbc0801e7be56f9a1ec11/>
*** Diff to previous build ***
============================
PASS -> UNRESOLVED: gdb.dwarf2/multidictionary.exp: GDB is alive
PASS -> FAIL: gdb.reverse/s390-mvcle.exp: check MVCLE record 3
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=16: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=17: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=18: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=19: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=3: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=4: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=6: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=8: wait for stops
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Add the "set style source" command
@ 2019-03-14 12:55 sergiodj+buildbot
2019-03-14 18:35 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-14 12:55 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT cf2a5276288ce16242a35594db9f61fa9e8f5120 ***
Author: Tom Tromey <tromey@adacore.com>
Branch: gdb-8.3-branch
Commit: cf2a5276288ce16242a35594db9f61fa9e8f5120
Add the "set style source" command
This adds "set style source" (and "show style source") commands. This
gives the user control over whether source code is highlighted.
2019-03-14 Tom Tromey <tromey@adacore.com>
* NEWS: Add item for "style sources" commands.
* source-cache.c (source_cache::get_source_lines): Check
source_styling.
* cli/cli-style.c (source_styling): New global.
(_initialize_cli_style): Add "style sources" commands.
(show_style_sources): New function.
* cli/cli-style.h (source_styling): Declare.
gdb/doc/ChangeLog
2019-03-14 Tom Tromey <tromey@adacore.com>
* gdb.texinfo (Output Styling): Document "set style source" and
"show style source".
gdb/testsuite/ChangeLog
2019-03-14 Tom Tromey <tromey@adacore.com>
* gdb.base/style.exp: Add "set style sources" test.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Make TUI react to "set style enabled"
@ 2019-03-14 12:41 sergiodj+buildbot
2019-03-14 17:14 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-14 12:41 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 3768f5bdec2ed46e7c3c07c863cebd99a5efe645 ***
Author: Tom Tromey <tromey@adacore.com>
Branch: gdb-8.3-branch
Commit: 3768f5bdec2ed46e7c3c07c863cebd99a5efe645
Make TUI react to "set style enabled"
When the user toggles "set style enabled", the TUI should react by
redrawing the source window, if necessary. This patch implements this
behavior.
No test because the TUI is generally not tested.
This version of the patch incorporates Pedro's patch to provide a
clean way to force the TUI to update the source window's contents.
2019-03-14 Pedro Alves <palves@redhat.com>
Tom Tromey <tromey@adacore.com>
* tui/tui-winsource.h (tui_refill_source_window): Declare.
* tui/tui-winsource.c (tui_refill_source_window): New function,
from...
(tui_horizontal_source_scroll): ... here. Move some logic.
* cli/cli-style.c (set_style_enabled): Notify new observable.
* tui/tui-hooks.c (tui_redisplay_source): New function.
(tui_attach_detach_observers): Attach or detach
tui_redisplay_source.
* observable.h (source_styling_changed): New observable.
* observable.c: Define source_styling_changed observable.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix MinGW build with source-highlight
@ 2019-03-12 18:13 sergiodj+buildbot
2019-03-13 1:36 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-12 18:13 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 4a9e44628b32c26e91aa480ae93db4432ed8d957 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 4a9e44628b32c26e91aa480ae93db4432ed8d957
Fix MinGW build with source-highlight
gdb/ChangeLog
2019-03-12 Eli Zaretskii <eliz@gnu.org>
PR/24325
* source-cache.c: #undef open and close, to avoid unresolved
externals during linking.
(cherry picked from commit 3a3508220eecf27e1952a73cd3ea6d6314ce8e1d)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Support styling on native MS-Windows console
@ 2019-03-09 7:14 sergiodj+buildbot
2019-03-09 9:16 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-09 7:14 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 1778a983e2f31181644b7574b8d062e4be22e813 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 1778a983e2f31181644b7574b8d062e4be22e813
Support styling on native MS-Windows console
gdb/ChangeLog:
2019-03-08 Eli Zaretskii <eliz@gnu.org>
PR/24315
* utils.c (can_emit_style_escape) [_WIN32]: Don't disable styling
on MS-Windows if $TERM is not defined.
* cli/cli-style.c: Set cli_styling to 1 in the MinGW build.
* posix-hdep.c (gdb_console_fputs):
* mingw-hdep.c (rgb_to_16colors, gdb_console_fputs): New
functions.
* ui-file.h (gdb_console_fputs): Add prototype.
* ui-file.c (stdio_file::puts): Call gdb_console_fputs, and fall
back to fputs only if the former returns zero.
(cherry picked from commit e4adb93903d4ae0b7ab2b5004364e50627df95f7)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Can't interrupt process without controlling terminal on Solaris (PR gdb/8527)
@ 2019-03-07 21:15 sergiodj+buildbot
2019-03-08 19:02 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-07 21:15 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 6028d151fc820579da1292c4cc393a4bcd3da8f8 ***
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: gdb-8.3-branch
Commit: 6028d151fc820579da1292c4cc393a4bcd3da8f8
Can't interrupt process without controlling terminal on Solaris (PR gdb/8527)
If gdb attaches to a process that either has no controlling terminal,
or the controlling terminal differs from the one gdb is running under,
break/^C doesn't interrupt the debugged process on Solaris.
Fixed as follows, analogous to what all all other targets do. Patch from
the PR, recently re-submitted by Brian Vandenberg.
Tested on amd64-pc-solaris2.11, sparcv9-sun-solaris2.11, and
x86_64-pc-linux-gnu.
2019-03-07 Brian Vandenberg <phantall@gmail.com>
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
gdb:
PR gdb/8527
* procfs.c (proc_wait_for_stop): Wrap write of PCWSTOP in
set_sigint_trap, clear_sigint_trap.
gdb/testsuite:
PR gdb/8527
* gdb.base/interrupt-daemon-attach.c,
gdb.base/interrupt-daemon-attach.exp: New test.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Testsuite: Ensure changing directory does not break the log file
@ 2019-03-06 10:29 sergiodj+buildbot
2019-03-06 13:57 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-06 10:29 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 9b068afad22bfa9386b21762c91eaddd8ef691b4 ***
Author: Alan Hayward <alan.hayward@arm.com>
Branch: gdb-8.3-branch
Commit: 9b068afad22bfa9386b21762c91eaddd8ef691b4
Testsuite: Ensure changing directory does not break the log file
get_compiler_info switches to a new log file before checking the compiler
to ensure the checks are not logged. Afterwards it restores back to using
the original log file. However, the logfile uses a relative path name -
if the current test has changed the current directory then all further
output for the test will be lost. This can confuse the code that collates
the main gdb.log file at the end of a FORCE_PARALLEL run.
fullpath-expand.exp calls gdb_compile after changing the current directory.
The "Ensure stack protection is off for GCC" patch added a call to
get_compiler_info from inside of gdb_compile, causing log file collection
to break for FORCE_PARALLEL runs.
The ideal solution would be to ensure the log file is always created using
an absolute path name. However, this is set at multiple points in
Makefile.in and in some instances just relies on dejagnu common code to set
the log file directory to "."
The simpler and safer solution is to override the builtin cd function. The
new function checks the current log file and if the path is relative, then
it resets the logging using an absolute path. Finally it calls the builtin
cd. This ensures get_compiler_info (and any other code) can correctly
backup and restore the current log file.
gdb/testsuite/ChangeLog:
* lib/gdb.exp (builtin_cd): rename of cd.
(cd): Override builtin.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Use '$enable_unittest' instead of '$development' on gdbserver/configure.srv (for 'aarch64*-*-linux*' case)
@ 2019-03-05 17:52 sergiodj+buildbot
2019-03-06 5:09 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-05 17:52 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 24329b66c90f1f51c96e718fe6533af3a3b4aa47 ***
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: gdb-8.3-branch
Commit: 24329b66c90f1f51c96e718fe6533af3a3b4aa47
Use '$enable_unittest' instead of '$development' on gdbserver/configure.srv (for 'aarch64*-*-linux*' case)
On commit 8ecfd7bd4acd69213c06fac6de9af38299123547 ("Add parameter to
allow enabling/disabling selftests via configure") it seems that I
forgot to use the proper '$enable_unittest' variable when checking to
see whether to add selftest-related objects to 'srv_regobj'. This
causes a build failure on Aarch64 when 'development=false' (which is
the case for the 8.3 branch) and 'enable_unittest=true'.
This patch fixes the problem by using '$enable_unittest' instead of
'$development' when performing the check. As a reminder, it's
important to notice that '$enable_unittest's default value (i.e., when
the option '--enable-unit-tests' is not passed to configure) is the
same as '$development', so this patch doesn't affect the current
build.
I'd like to install this patch both on master and on the 8.3 branch.
OK?
gdb/gdbserver/ChangeLog:
2019-03-04 Sergio Durigan Junior <sergiodj@redhat.com>
* configure.srv: Use '$enable_unittest' instead of '$development'
when checking whether to fill 'srv_regobj' on 'aarch64*-*-linux*'
case.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Avoid compilation warnings on MinGW.
@ 2019-03-02 14:32 sergiodj+buildbot
2019-03-02 21:01 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-02 14:32 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 4344b2225c8d4878a27401b94ec6315c728f46bf ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 4344b2225c8d4878a27401b94ec6315c728f46bf
Avoid compilation warnings on MinGW.
gdb/ChangeLog:
2019-03-02 Eli Zaretskii <eliz@gnu.org>
* xml-syscall.c (xml_list_syscalls_by_group): Drop 'struct' from
for-loop range, to avoid compiler warnings.
* tui/tui.c (tui_enable) [__MINGW32__]: Don't declare 'cap', to
avoid compiler warnings about unused variables.
(cherry picked from commit a6a4b2c636b29de09dea890b448f99804ef7bc18)
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-03-02 14:32 [binutils-gdb/gdb-8.3-branch] Avoid compilation warnings on MinGW sergiodj+buildbot
@ 2019-03-02 21:01 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-02 21:01 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7517>
Commit(s) tested:
4344b2225c8d4878a27401b94ec6315c728f46bf
Author(s) (in the same order as the commits):
Eli Zaretskii <eliz@gnu.org>
Subject:
Avoid compilation warnings on MinGW.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/43/4344b2225c8d4878a27401b94ec6315c728f46bf/>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.reverse/s390-mvcle.exp: check MVCLE record 3
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=16: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=1: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=4: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=6: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=8: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=9: wait for stops
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=0: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] GDB no longer supports Windows before XP.
@ 2019-03-02 14:21 sergiodj+buildbot
2019-03-02 19:44 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-02 14:21 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 0db97a309b840fa59b0348049082b850702639e2 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 0db97a309b840fa59b0348049082b850702639e2
GDB no longer supports Windows before XP.
gdb/ChangeLog:
2019-03-02 Eli Zaretskii <eliz@gnu.org>
* NEWS: Mention end of support for native debugging on MS-Windows
before XP.
(cherry picked from commit 742a7df5f4a149f0818aaccfc432c4c0c9a6e26d)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Fix GDB compilation on MinGW (PR gdb/24292)
@ 2019-03-02 14:11 sergiodj+buildbot
2019-03-02 18:25 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-03-02 14:11 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 654c8256bb9e083b3dcdd6205d6ecbc6beddb00e ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: gdb-8.3-branch
Commit: 654c8256bb9e083b3dcdd6205d6ecbc6beddb00e
Fix GDB compilation on MinGW (PR gdb/24292)
gdb/ChangeLog:
2019-03-02 Eli Zaretskii <eliz@gnu.org>
PR gdb/24292
* common/netstuff.c:
* gdbserver/gdbreplay.c
* gdbserver/remote-utils.c:
* ser-tcp.c:
* unittests/parse-connection-spec-selftests.c [USE_WIN32API]:
Include ws2tcpip.h instead of wsiapi.h and winsock2.h. Redefine
_WIN32_WINNT to 0x0501 if defined to a smaller value, as
'getaddrinfo' and 'freeaddrinfo' were not available before
Windows XP, and mingw.org's MinGW headers by default define
_WIN32_WINNT to 0x500.
(cherry picked from commit 41fa577fbc326402be49b3f03bc828e52dba8b88)
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Document fact that mininum Python version is now 2.6
@ 2019-02-27 19:49 sergiodj+buildbot
2019-02-28 23:51 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-02-27 19:49 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT 7008bd663c7b314d9177044bb70fd39d4103e2c4 ***
Author: Kevin Buettner <kevinb@redhat.com>
Branch: gdb-8.3-branch
Commit: 7008bd663c7b314d9177044bb70fd39d4103e2c4
Document fact that mininum Python version is now 2.6
gdb/ChangeLog:
* NEWS: Note minimum Python version.
gdb/doc/ChangeLog:
* gdb.texinfo (Configure Options): Document minimum python
version.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Bump GDB version number to 8.2.90.DATE-git.
@ 2019-02-27 6:22 sergiodj+buildbot
2019-02-27 15:59 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-02-27 6:22 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT e94d66159e5a0d7e574466343b14ee3da7814da1 ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: e94d66159e5a0d7e574466343b14ee3da7814da1
Bump GDB version number to 8.2.90.DATE-git.
gdb/ChangeLog:
* version.in: Set GDB version number to 8.2.90.DATE-git.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Set GDB version number to 8.2.90.
@ 2019-02-27 6:11 sergiodj+buildbot
2019-02-27 14:41 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-02-27 6:11 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT c77cdfe6472414713071709731fe3b7041f8608e ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: c77cdfe6472414713071709731fe3b7041f8608e
Set GDB version number to 8.2.90.
gdb/ChangeLog:
* version.in: Set GDB version number to 8.2.90.
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] change section name in gdb/NEWS for changes in GDB 8.3
@ 2019-02-27 5:59 sergiodj+buildbot
2019-02-27 13:16 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-02-27 5:59 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT d05bcc0f7696eb2e33779f13701c4af10eed0e89 ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: d05bcc0f7696eb2e33779f13701c4af10eed0e89
change section name in gdb/NEWS for changes in GDB 8.3
gdb/ChangeLog:
* NEWS: Change "Changes since GDB 8.2" into "Changes in GDB 8.3".
^ permalink raw reply [flat|nested] 56+ messages in thread
* [binutils-gdb/gdb-8.3-branch] Set development mode to "off" by default.
@ 2019-02-27 5:26 sergiodj+buildbot
2019-02-27 9:15 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
0 siblings, 1 reply; 56+ messages in thread
From: sergiodj+buildbot @ 2019-02-27 5:26 UTC (permalink / raw)
To: gdb-testers
*** TEST RESULTS FOR COMMIT c96a77fd206679a62db8912f0219d69b31ea3fe6 ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: gdb-8.3-branch
Commit: c96a77fd206679a62db8912f0219d69b31ea3fe6
Set development mode to "off" by default.
bfd/ChangeLog:
* development.sh (development): Set to false.
^ permalink raw reply [flat|nested] 56+ messages in thread
* Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch
2019-02-27 5:26 [binutils-gdb/gdb-8.3-branch] Set development mode to "off" by default sergiodj+buildbot
@ 2019-02-27 9:15 ` sergiodj+buildbot
0 siblings, 0 replies; 56+ messages in thread
From: sergiodj+buildbot @ 2019-02-27 9:15 UTC (permalink / raw)
To: gdb-testers
Buildslave:
debian-jessie-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-native-gdbserver-m64/builds/7470>
Commit(s) tested:
c96a77fd206679a62db8912f0219d69b31ea3fe6
Author(s) (in the same order as the commits):
Joel Brobecker <brobecker@adacore.com>
Subject:
Set development mode to "off" by default.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Debian-s390x-native-gdbserver-m64/c9/c96a77fd206679a62db8912f0219d69b31ea3fe6/>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.reverse/s390-mvcle.exp: check MVCLE record 3
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=11: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=12: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=13: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=16: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=17: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=18: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=19: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=5: wait for stops
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.
^ permalink raw reply [flat|nested] 56+ messages in thread
end of thread, other threads:[~2019-05-13 20:21 UTC | newest]
Thread overview: 56+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-18 15:12 [binutils-gdb/gdb-8.3-branch] Fix scrolling right in the TUI sergiodj+buildbot
2019-03-18 15:12 ` Failures on RHEL-s390x-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-18 19:43 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-03-18 20:19 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2019-03-18 20:41 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2019-03-24 1:44 ` Failures on Fedora-i686, " sergiodj+buildbot
2019-03-24 1:51 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2019-03-24 2:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-03-24 2:50 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2019-03-24 3:14 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2019-03-24 3:19 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2019-03-26 3:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2019-03-26 14:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
-- strict thread matches above, loose matches on Subject: below --
2019-05-11 18:58 [binutils-gdb/gdb-8.3-branch] Bump GDB version number to 8.3.0.DATE-git sergiodj+buildbot
2019-05-13 20:51 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-05-11 18:40 [binutils-gdb/gdb-8.3-branch] Set GDB version number to 8.3 sergiodj+buildbot
2019-05-13 18:30 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-05-08 17:50 [binutils-gdb/gdb-8.3-branch] Fix style bug when paging sergiodj+buildbot
2019-05-09 0:44 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-05-04 20:48 [binutils-gdb/gdb-8.3-branch] Don't derive partial_symbol from general_symbol_info sergiodj+buildbot
2019-05-05 2:52 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-05-03 8:22 [binutils-gdb/gdb-8.3-branch] Fix compilation with mingw.org's MinGW sergiodj+buildbot
2019-05-03 14:32 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-05-03 8:07 [binutils-gdb/gdb-8.3-branch] Fix lookup of separate debug file on MS-Windows sergiodj+buildbot
2019-05-03 12:17 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-05-03 7:23 [binutils-gdb/gdb-8.3-branch] Treat the .gnu.debuglink and .gnu.debugaltlink sections as debug sections when reading them in from COFF/PE format files sergiodj+buildbot
2019-05-03 8:07 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-04-30 21:20 [binutils-gdb/gdb-8.3-branch] (Windows) fix thr != nullptr assert failure in delete_thread_1 sergiodj+buildbot
2019-05-01 12:02 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-04-30 14:56 [binutils-gdb/gdb-8.3-branch] Fix crash in dwarf2read.c with template parameters sergiodj+buildbot
2019-05-01 6:08 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-04-20 16:55 [binutils-gdb/gdb-8.3-branch] gdb/configure.ac: add --enable-source-highlight sergiodj+buildbot
2019-04-21 7:49 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-04-20 16:08 [binutils-gdb/gdb-8.3-branch] Fix "list" when control characters are seen sergiodj+buildbot
2019-04-21 1:31 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-04-20 15:20 [binutils-gdb/gdb-8.3-branch] Fix GDB 8.3 regression crash when registers cannot be modified sergiodj+buildbot
2019-04-20 20:07 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-04-12 13:08 [binutils-gdb/gdb-8.3-branch] Another fix for GDB styling sergiodj+buildbot
2019-04-14 16:08 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-28 18:47 [binutils-gdb/gdb-8.3-branch] Fix testsuite hangs when gdb_test_multiple body errors out sergiodj+buildbot
2019-03-29 6:43 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-27 1:03 [binutils-gdb/gdb-8.3-branch] Bump GDB version number to 8.2.91.DATE-git sergiodj+buildbot
2019-03-27 18:56 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-27 0:32 [binutils-gdb/gdb-8.3-branch] Set GDB version number to 8.2.91 sergiodj+buildbot
2019-03-27 16:01 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-26 23:59 [binutils-gdb/gdb-8.3-branch] gdb/testsuite: Prepare for DejaGnu 1.6.2 sergiodj+buildbot
2019-03-27 14:35 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-26 22:00 [binutils-gdb/gdb-8.3-branch] Merge handle_inferior_event and handle_inferior_event_1 sergiodj+buildbot
2019-03-27 9:47 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-26 1:15 [binutils-gdb/gdb-8.3-branch] Fix use-after-free in source_cache::get_source_lines sergiodj+buildbot
2019-03-26 12:00 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-18 19:27 [binutils-gdb/gdb-8.3-branch] Fix first time you type UP or DOWN in TUI's command window sergiodj+buildbot
2019-03-19 6:12 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-18 18:37 [binutils-gdb/gdb-8.3-branch] Fix gdb/TUI behavior in response to [Enter] keypress sergiodj+buildbot
2019-03-19 2:56 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-18 15:25 [binutils-gdb/gdb-8.3-branch] Improve/fix the TUI's current source line highlight sergiodj+buildbot
2019-03-18 21:58 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-17 16:32 [binutils-gdb/gdb-8.3-branch] Fix redisplay of the current line in GDB TUI mode sergiodj+buildbot
2019-03-17 18:54 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-16 18:28 [binutils-gdb/gdb-8.3-branch] Fix vertical scrolling of TUI source window sergiodj+buildbot
2019-03-17 3:31 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-16 12:45 [binutils-gdb/gdb-8.3-branch] Revert "Use wclrtoeol in tui_show_source_line" sergiodj+buildbot
2019-03-16 22:27 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-14 16:38 [binutils-gdb/gdb-8.3-branch] The NEWS file had two "New targets" sections for 8.3 sergiodj+buildbot
2019-03-15 2:56 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-14 15:49 [binutils-gdb/gdb-8.3-branch] Fix colors in TUI mode in MS-Windows build with ncurses sergiodj+buildbot
2019-03-14 22:48 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-14 13:08 [binutils-gdb/gdb-8.3-branch] Avoid a crash in source_cache::extract_lines sergiodj+buildbot
2019-03-14 19:59 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-14 12:55 [binutils-gdb/gdb-8.3-branch] Add the "set style source" command sergiodj+buildbot
2019-03-14 18:35 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-14 12:41 [binutils-gdb/gdb-8.3-branch] Make TUI react to "set style enabled" sergiodj+buildbot
2019-03-14 17:14 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-12 18:13 [binutils-gdb/gdb-8.3-branch] Fix MinGW build with source-highlight sergiodj+buildbot
2019-03-13 1:36 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-09 7:14 [binutils-gdb/gdb-8.3-branch] Support styling on native MS-Windows console sergiodj+buildbot
2019-03-09 9:16 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-07 21:15 [binutils-gdb/gdb-8.3-branch] Can't interrupt process without controlling terminal on Solaris (PR gdb/8527) sergiodj+buildbot
2019-03-08 19:02 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-06 10:29 [binutils-gdb/gdb-8.3-branch] Testsuite: Ensure changing directory does not break the log file sergiodj+buildbot
2019-03-06 13:57 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-05 17:52 [binutils-gdb/gdb-8.3-branch] Use '$enable_unittest' instead of '$development' on gdbserver/configure.srv (for 'aarch64*-*-linux*' case) sergiodj+buildbot
2019-03-06 5:09 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-02 14:32 [binutils-gdb/gdb-8.3-branch] Avoid compilation warnings on MinGW sergiodj+buildbot
2019-03-02 21:01 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-02 14:21 [binutils-gdb/gdb-8.3-branch] GDB no longer supports Windows before XP sergiodj+buildbot
2019-03-02 19:44 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-03-02 14:11 [binutils-gdb/gdb-8.3-branch] Fix GDB compilation on MinGW (PR gdb/24292) sergiodj+buildbot
2019-03-02 18:25 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-02-27 19:49 [binutils-gdb/gdb-8.3-branch] Document fact that mininum Python version is now 2.6 sergiodj+buildbot
2019-02-28 23:51 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-02-27 6:22 [binutils-gdb/gdb-8.3-branch] Bump GDB version number to 8.2.90.DATE-git sergiodj+buildbot
2019-02-27 15:59 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-02-27 6:11 [binutils-gdb/gdb-8.3-branch] Set GDB version number to 8.2.90 sergiodj+buildbot
2019-02-27 14:41 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-02-27 5:59 [binutils-gdb/gdb-8.3-branch] change section name in gdb/NEWS for changes in GDB 8.3 sergiodj+buildbot
2019-02-27 13:16 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-branch sergiodj+buildbot
2019-02-27 5:26 [binutils-gdb/gdb-8.3-branch] Set development mode to "off" by default sergiodj+buildbot
2019-02-27 9:15 ` Failures on Debian-s390x-native-gdbserver-m64, branch gdb-8.3-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).