[Bug testsuite/29664] [gdb/testsuite, taskset -c 0] FAIL: gdb.base/style.exp: capture_command_output for x/1i *main

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29664

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
A minimal reproducer:
...
$ cat gdb/testsuite/gdb.base/style.exp 
load_lib gdb-python.exp

clean_restart

gdb_py_test_silent_cmd \
    [multi_line_input \
         "python" \
         "\004"] \
    "python, ^D" \
    true

set command "print 1"

set test "capture_command_output for $command"

set re_command [string_to_regexp ${command}]
gdb_test_multiple "$command" "$test - match command" {
    -re "^$re_command\r\n" {
        pass $gdb_test_name
    }
}

gdb_test_multiple "" "$test - match output" {
    -re "^(\[^\r\n\]+\r\n)" {
        exp_continue
    }
    -re "^$gdb_prompt $" {
        pass $gdb_test_name
    }
}
...

I think there's a bug in the fact that we're handling a single command output
using two gdb_test_multiples.

But I think the root cause here is another one: we're using
gdb_py_test_silent_cmd to send a command ending in ^D, but doing so adds a "\n"
at the end.

This fixes it:
...
set command \
    [multi_line_input \
         "python" \
         "\004"]
send_gdb $command
gdb_py_test_silent_cmd \
    "" \
    "python, ^D" \
    true
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.