This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA 0/5] some cleanup removal for ui_out
- From: Tom Tromey <tom at tromey dot com>
- To: Tom Tromey <tom at tromey dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 22 Apr 2017 09:44:46 -0600
- Subject: Re: [RFA 0/5] some cleanup removal for ui_out
- Authentication-results: sourceware.org; auth=none
- References: <20170414022337.28368-1-tom@tromey.com>
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This series converts various (easy) spots to use ui_out_emit_list or
Tom> ui_out_emit_tuple. This removes a number of cleanups.
I am finally going to check this in.
I hadn't done so earlier because my buildbot runs were occasionally
showing some failures. However, a recent run with a completely
different patch shows the same failures, so I'm going forward on the
theory that these patches of mine aren't causing the problem.
The failures I'm seeing are from gdb.mi/user-selected-context-sync.exp,
though exactly which failures are seen varies by run.
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_frame: thread 1.2: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_select_frame: thread 1.2: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_cli_up_down: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: test_mi_stack_select_frame: thread 1.2: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=direct: test_cli_in_mi_frame: thread 1.2: reset selection to thread 1.2
PASS -> FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop: exec_mode=interpreter-exec: test_cli_in_mi_frame: thread 1.2: reset selection to thread 1.2
Tom