Re: [PATCH] Fix gdb crash with tui

[Pedro Alves <palves at redhat dot com>]

On 03/12/2013 04:03 PM, Pedro Alves wrote:
> On 03/12/2013 12:36 PM, Jan Kratochvil wrote:
>> On Tue, 12 Mar 2013 13:21:44 +0100, Hui Zhu wrote:
>>> Not sure the prev backtrace for crash is right, so I post new one:
>>
>> BTW don't you have a recipe for the reproducibility?  Don't you have some
>> unusual terminal size (stty size) for example?  Which distro?
>>
>>
>> Jan
> 
> I just reproduced it on my Fedora 17 box with current mainline.
> 
> $ stty size
> 45 172
> 
> To reproduce, I just did the steps in the OP.
> 
> $ ./gdb ./gdb
> (gdb) start
> 
> "c-x a" to flip to TUI mode.
> 
> repeat:
>  press arrow up a bit, so the source display scrolls a bit up.
>  press arrow down a bit, so the source display scrolls a bit down.
>  goto repeat until
> 
>  "---Type <return> to continue, or q <return> to quit---"
> 
> appears in TUI's console.  Then press return.

Valgrind log appended (w/ valgrind --log-file=valgrind.log ./gdb ./gdb).

Suspecting this to be some rounding error, I tried with
44 columns, but I get the same.

Running under valgrind, however, since things run much
slower, it's noticeable that GDB occasionally prints the
source file name at the wrong place -- we see it
flashing under the cursor in the console window.

I don't know if that's the source file name that's supposed
to go to the top left, or if it's an extra rogue source file
name that should not be printed at all in the tui.

I don't see that flash without valgrind.

-- 
Pedro Alves

Attachment: valgrind.log.gz
Description: GNU Zip compressed data