[Bug tui/15581] New: TUI assembly window line display problem with potential crash

[adrianh.bsc at gmail dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=15581

Bug ID: 15581
Summary: TUI assembly window line display problem with
potential crash
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: adrianh.bsc at gmail dot com

When the line prefix is too long, the address goes wonky. I.e. the leading 0
for an address is skipped every other line causing a sawtooth pattern. (See
Loading Image...).

Also, I had the debugger crash when using the `next` command while having the
ASM window open or scrolling the ASM or CMD windows around, presumably due to
some buffer overrun problem as it would appear that some of the lines are still
fully displayed and then written over. In the case of `next`, the current line
is fully displayed and wrapped around the end of the screen
(Loading Image...).

[adrianh.bsc at gmail dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=15581

--- Comment #1 from Adrian <adrianh.bsc at gmail dot com> ---
The sawtooth pattern is caused by incorrect positioning of the line one
character to the left and then having the boarder redraw over top of it,
removing the leading 0.

[palves at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=15581

Pedro Alves <palves at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |palves at redhat dot com

--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
I think this has been addressed in current master (soon to be 7.10). Could you
confirm?

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=15581

Tom Tromey <tromey at sourceware dot org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |tromey at sourceware dot org
Resolution|--- |FIXED

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Believed to have been fixed, and several years without feedback.
Feel free to reopen if it is still a problem.