Re: [PATCH 1/1] testsuite: skip confirmation in 'gdb_reinitialize_dir'

[Eli Zaretskii <eliz@gnu.org>]

> From: "Rohr, Stephan" <stephan.rohr@intel.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> Date: Thu, 14 Nov 2024 16:30:26 +0000
> 
> I further investigated the issue.  The issue is triggered if "TERM=dump" is set in a MinGW
> environment.  I can reproduce the issue in CLI mode, too:
> 
>   $ ./gdb -q
>   (gdb) dir
>   Reinitialize source path to empty? (y or n) [answered Y; input not from terminal]
>   Source directories searched: $cdir;$cwd
>   (gdb)

Strange, it doesn't happen here, at least not when I run GDB from
cmd.exe after setting TERM=dumb.

> I used the setting to workaround some issues when running tests on Windows using
> MinGW.  I can see that control characters are added to the output of different commands,
> e.g., 'test_compiler_info' fails with:
> 
>   builtin_spawn -ignore SIGHUP gcc -fdiagnostics-color=never -c -o ...
>   ^[[6nget_compiler_info: gcc-14-2-0
>   get_compiler_info: gcc-14-2-0
>   Executing on host: gcc  -fno-stack-protector  -w -c -g  -o ...
>   builtin_spawn -ignore SIGHUP gcc -fno-stack-protector -w -c -g -o ...
>   ^[[6noutput is:
>   ^[[6n
>   gdb compile failed, ^[[6n
> 
> I haven't understood yet why this is added in MinGW or how to disable those.
> 
> The patch enables me to run the tests I'm interested in in a MinGW environment.

OK, if that affects only the test suite and only in some environments,
I guess the change cannot do any harm.

Thanks.