diff options
| author | Tom de Vries <tdevries@suse.de> | 2025-06-17 08:28:50 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2025-06-17 08:28:50 +0200 |
| commit | 7e1964f9c61c2a508d955ce603800cb894ac937f (patch) | |
| tree | 1529ce0fae31e92ad10e658c22fcf858394530e4 /gdb/testsuite/gdb.python/py-error.py | |
| parent | 420aa637808fa3f91389e801a516a6c0b1471563 (diff) | |
| download | binutils-7e1964f9c61c2a508d955ce603800cb894ac937f.zip binutils-7e1964f9c61c2a508d955ce603800cb894ac937f.tar.gz binutils-7e1964f9c61c2a508d955ce603800cb894ac937f.tar.bz2 | |
[gdb/testsuite] Set TERM to dumb by default
With MSYS2 and default TERM=xterm-256color (as well as with xterm and ansi), I
get:
...
builtin_spawn gdb -q ...
^[[6n(gdb) ERROR: GDB never initialized.
...
This is not specific to gdb, other tools produce the same CSI sequence, and
consequently we run into trouble in other places (like get_compiler_info).
Fix this by default-setting TERM to dumb.
We do this for all platforms, to avoid test-cases passing on one platform but
failing on another.
For test-cases that set TERM to something other than dumb, handle the CSI
sequence in default_gdb_start.
Approved-By: Tom Tromey <tom@tromey.com>
PR testsuite/33072
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33072
Diffstat (limited to 'gdb/testsuite/gdb.python/py-error.py')
0 files changed, 0 insertions, 0 deletions