aboutsummaryrefslogtreecommitdiff
path: root/bfd
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2019-03-18 18:32:42 +0000
committerPedro Alves <palves@redhat.com>2019-03-18 18:32:42 +0000
commit5371b8502ab414aea510f65ce1acb9f090bf0340 (patch)
tree8a3f07a01312543c9fabec5c10f11166ace1fd01 /bfd
parentb17c4cd078e2d1d8951951016815e474fb133780 (diff)
downloadgdb-5371b8502ab414aea510f65ce1acb9f090bf0340.zip
gdb-5371b8502ab414aea510f65ce1acb9f090bf0340.tar.gz
gdb-5371b8502ab414aea510f65ce1acb9f090bf0340.tar.bz2
Fix first time you type UP or DOWN in TUI's command window
The first time you type UP or DOWN arrow in the command window, GDB should scroll the source window, but instead it displays the line number and the file name in the command window(?). What happens there is that the first time we call tui_ui_out::do_field_int, it doesn't initialize m_line, because m_start_of_line is -1, as set by the constructor; and then the following call to tui_ui_out::do_field_string falls back to cli_ui_out::do_field_string because m_line is zero. The problem is caused by a typo in the C++ification of tui_ui_out, commit 112e8700a6f, where m_line and m_start_of_line's initial values were swapped from what they used to be: -struct ui_out * -tui_out_new (struct ui_file *stream) +tui_ui_out::tui_ui_out (ui_file *stream) +: cli_ui_out (stream, 0), + m_line (0), + m_start_of_line (-1) { - - /* Initialize our fields. */ - data->line = -1; - data->start_of_line = 0; This commit fixes it. gdb/ChangeLog: 2019-03-18 Pedro Alves <palves@redhat.com> Eli Zaretskii <eliz@gnu.org> * tui/tui-out.c (tui_ui_out::tui_ui_out): Fix initialization of m_line and m_start_of_line.
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions