From 56a731d4ad319e473851893980e734b7ee42c1a0 Mon Sep 17 00:00:00 2001 From: Jan Kratochvil Date: Fri, 8 Feb 2019 13:49:19 -0500 Subject: Avoid readline conflicts in pexpect In some cases, sensitive to readline version and the user's environment, gdb might emit escape codes while run under python's pexpect (i.e. testing pretty printers). This patch, suggested by Jan, helps isolate the test from the user's environment. Tested on RHEL 7 x86_64 with DTS 7 and EPEL, which is one magic combination of components that triggers this bug. --- scripts/test_printers_common.py | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'scripts') diff --git a/scripts/test_printers_common.py b/scripts/test_printers_common.py index dada6aadde..b2bd4ba1cc 100644 --- a/scripts/test_printers_common.py +++ b/scripts/test_printers_common.py @@ -60,6 +60,10 @@ TIMEOUTFACTOR = os.environ.get('TIMEOUTFACTOR') if TIMEOUTFACTOR: timeout = int(TIMEOUTFACTOR) +# Otherwise GDB is run in interactive mode and readline may send escape +# sequences confusing output for pexpect. +os.environ["TERM"]="dumb" + try: # Check the gdb version. version_cmd = '{0} --version'.format(gdb_invocation, timeout=timeout) -- cgit 1.4.1