diff options
| author | Tom de Vries <tdevries@suse.de> | 2021-10-06 11:26:38 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2021-10-06 11:26:38 +0200 |
| commit | cf2ad3e66286c9f3dc8cb6cf74a2af761cb7a49f (patch) | |
| tree | 1ca193b0919b1e3f10f629e8874ceec982376ff3 /gdb/rust-lang.c | |
| parent | 1992e26ec4498bdd08fa960b449f6fa29e5759fa (diff) | |
| download | gdb-cf2ad3e66286c9f3dc8cb6cf74a2af761cb7a49f.zip gdb-cf2ad3e66286c9f3dc8cb6cf74a2af761cb7a49f.tar.gz gdb-cf2ad3e66286c9f3dc8cb6cf74a2af761cb7a49f.tar.bz2 | |
[gdb/testsuite] Fix FAIL in gdb.tui/corefile-run.exp
When running test-case gdb.tui/corefile-run.exp on openSUSE Tumbleweed,
I run into:
...
PASS: gdb.tui/corefile-run.exp: load corefile
FAIL: gdb.tui/corefile-run.exp: run until the end
...
What's going on is easier to see when also doing dump_screen if
check_contents passes, and inspecting state at the preceding PASS:
...
+-------------------------------------------------------------------------+
exec No process In: L?? PC: ??
[New LWP 16629]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/data/gdb_versions/devel/build/gdb/testsuite/output
s/gdb.tui/corefile-run/corefi'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0 main ()
--Type <RET> for more, q to quit, c to continue without paging--
...
The problem is that we're getting a pagination prompt, and the subsequent run
command is interpreted as an answer to that prompt.
Fix this by:
- detecting the gdb prompt in response to "load corefile", such that
we detect the failure earlier, and
- doing a "set pagination off" in Term::clean_restart.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/rust-lang.c')
0 files changed, 0 insertions, 0 deletions