[PATCH] gdb: Don't change the uiout to console one when doing gdb.execute in TUI

[Marco Barisione]

On 24 May 2021, at 19:25, Keith Seitz <keiths@redhat.com> wrote:
>> +# We can't use Term::command and Term::check_contents as that drops the
>> +# ANSI escape codes.
>> +send_gdb "${gdb_execute_backtrace}\n"
>> +set test_name "backtrace from gdb.execute with TUI"
>> +gdb_expect {
>> +  -re $expected_backtrace_styled_output {
>> +    pass $test_name
>> +  }
>> +  timeout {
>> +    fail $test_name
>> +  }
>> +}
>> 
> 
> We normally use gdb_test instead of gdb_send/gdb_expect. Is it not possible here?

I couldn’t get it to work in TUI mode and I couldn’t understand why (but
I’m not an expert in TCL or how printing works in TUI mode).  I will try
again as the test code is now simpler than it used to be while I was
developing the test and, if I cannot get gdb_test to work, I will add
a comment.

-- 
Marco Barisione