diff options
| author | Tom Tromey <tom@tromey.com> | 2023-12-12 19:22:07 -0700 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2024-03-11 16:27:26 -0600 |
| commit | 0a909fdd47b94e2d2fd9c0387fb644a98cb35d3b (patch) | |
| tree | 1d0ff21d200755fde75cd1547bc18cf129f7082a /libbacktrace/mtest.c | |
| parent | 0824937af0c0822e629a7076c3f5dd39df3b16be (diff) | |
| download | gdb-0a909fdd47b94e2d2fd9c0387fb644a98cb35d3b.zip gdb-0a909fdd47b94e2d2fd9c0387fb644a98cb35d3b.tar.gz gdb-0a909fdd47b94e2d2fd9c0387fb644a98cb35d3b.tar.bz2 | |
Remove tui-out.[ch]
The other day on irc, we were discussing the "m_line" hack in
tui-out.c, and I mentioned that it would be nice to replace this with
a new ui_out_flag.
Later, I looked at ui_out_flag and found:
ui_source_list = (1 << 0),
... and sure enough, this is tested already.
This patch removes tui-out.[ch] and changes the TUI to use an ordinary
cli-out object without this flag set.
As far as I can tell, this doesn't affect behavior at all -- the TUI
tests all pass, and interactively I tried switching stack frames,
"list", etc, and it all seems to work.
New in v2: fixed the problem pointed out by Keith, and added a test
case for that scenario.
Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Diffstat (limited to 'libbacktrace/mtest.c')
0 files changed, 0 insertions, 0 deletions