The TUI has two types of windows derived from tui_source_window_base:
- tui_source_window (the source window), and
- tui_disasm_window (the disassembly window).
The two windows share a common concept: the left margin.
With a hello world a.out, we can see the source window:
...
┌─/home/vries/hello.c───────────────────────────────────────┐
│ 5 { │
│B+> 6 printf ("hello\n"); │
│ 7 return 0; │
│ 8 } │
│ 9 │
│
...
where the left margin is the part holding "B+>" and the line number, and the
disassembly window:
...
┌───────────────────────────────────────────────────────────┐
│ 0x555555555149 <main> endbr64 │
│ 0x55555555514d <main+4> push %rbp │
│ 0x55555555514e <main+5> mov %rsp,%rbp │
│B+> 0x555555555151 <main+8> lea 0xeac(%rip),%rax│
│ 0x555555555158 <main+15> mov %rax,%rdi │
...
where the left margin is just the bit holding "B+>".
Because the left margin contains some spaces, it's not clear where it starts
and ends, making it harder to observe problems related to it.
Add a new maintenance command "maint set tui-left-margin-verbose", that when
set to on replaces the spaces in the left margin with either '_' or '0',
giving us this for the source window:
...
┌─/home/vries/hello.c───────────────────────────────────────┐
│___000005__{ │
│B+>000006__ printf ("hello\n"); │
│___000007__ return 0; │
│___000008__} │
...
and this for the disassembly window:
...
┌───────────────────────────────────────────────────────────┐
│___ 0x555555555149 <main> endbr64 │
│___ 0x55555555514d <main+4> push %rbp │
│___ 0x55555555514e <main+5> mov %rsp,%rbp │
│B+> 0x555555555151 <main+8> lea 0xeac(%rip),%rax│
│___ 0x555555555158 <main+15> mov %rax,%rdi │
...
Note the space between "B+>" and 0x555555555151. The space shows that a bit
of the left margin is not written, a problem reported as PR tui/30325.
Specifically, PR tui/30325 is about the fact that the '[' character from the
string "[ No Assembly Available ]" ends up in that same spot:
...
│B+>[0x555555555151 <main+8> lea 0xeac(%rip),%rax│
...
which only happens for certain window widths.
The new command allows us to spot the problem with any window width.
Likewise, when we revert the fix from commit
1b6d4bb2232 ("Redraw both spaces
between line numbers and source code"), we have:
...
┌─/home/vries/hello.c───────────────────────────────────────┐
│___000005_ { │
│B+>000006_ printf ("hello\n"); │
│___000007_ return 0; │
│___000008_ } │
...
showing a similar problem at the space between '_' and '{'.
Tested on x86_64-linux.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-By: Tom Tromey <tom@tromey.com>
where it would otherwise be difficult to determine when a resize and
refresh has been completed.
+@kindex maint set tui-left-margin-verbose
+@kindex maint show tui-left-margin-verbose
+@item maint set tui-left-margin-verbose
+@item maint show tui-left-margin-verbose
+Control whether the left margin of the TUI source and disassembly windows
+uses @samp{_} and @samp{0} at locations where otherwise there would be a
+space. The default is @code{off}, which means spaces are used. The
+setting is intended to make it clear where the left margin begins and
+ends, to avoid incorrectly interpreting a space as being part of the
+the left margin.
+
@kindex maint set per-command
@kindex maint show per-command
@item maint set per-command
char text[20];
/* To completely overwrite the previous border when the source window height
is increased, both spaces after the line number have to be redrawn. */
- xsnprintf (text, sizeof (text), "%*d ", m_digits - 1, lineno);
+ char space = tui_left_margin_verbose ? '_' : ' ';
+ xsnprintf (text, sizeof (text),
+ tui_left_margin_verbose ? "%0*d%c%c" : "%*d%c%c", m_digits - 1,
+ lineno, space, space);
waddstr (handle.get (), text);
}
help_list (tui_window_cmds, "tui window ", all_commands, gdb_stdout);
}
+/* See tui-win.h. */
+
+bool tui_left_margin_verbose = false;
+
/* Function to initialize gdb commands, for tui window
manipulation. */
&style_set_list,
&style_show_list);
+ add_setshow_boolean_cmd ("tui-left-margin-verbose", class_maintenance,
+ &tui_left_margin_verbose, _("\
+Set whether the left margin should use '_' and '0' instead of spaces."),
+ _("\
+Show whether the left margin should use '_' and '0' instead of spaces."),
+ _("\
+When enabled, the left margin will use '_' and '0' instead of spaces."),
+ nullptr,
+ nullptr,
+ &maintenance_set_cmdlist,
+ &maintenance_show_cmdlist);
+
tui_border_style.changed.attach (tui_rehighlight_all, "tui-win");
tui_active_border_style.changed.attach (tui_rehighlight_all, "tui-win");
}
current position indicator. */
extern bool style_tui_current_position;
+/* Whether to replace the spaces in the left margin with '_' and '0'. */
+extern bool tui_left_margin_verbose;
+
#endif /* TUI_TUI_WIN_H */
for (int i = 0; i < m_content.size (); i++)
{
struct tui_source_element *src_element = &m_content[i];
- char element[TUI_EXECINFO_SIZE] = " ";
+ char element[TUI_EXECINFO_SIZE];
+ /* Initialize all but last element. */
+ char space = tui_left_margin_verbose ? '_' : ' ';
+ memset (element, space, TUI_EXECINFO_SIZE - 1);
+ /* Initialize last element. */
+ element[TUI_EXECINFO_SIZE - 1] = '\0';
/* Now update the exec info content based upon the state
of each line as indicated by the source content. */