Re: Crash regression for annota1.exp w/vDSO debuginfo [Re: [pushed] Re: [PATCH v6 0/2] enable target-async by default]

Pedro Alves
2014-10-09T15:48:18Z

On 10/05/2014 03:00 PM, Jan Kratochvil wrote:
> On Thu, 29 May 2014 15:44:02 +0200, Pedro Alves wrote:
>> I went ahead and pushed this all in, with Eli's comments addressed.
>
> 329ea57934a9d4b250a0b417af1ec47bc2d0ceb6 is the first bad commit
> commit 329ea57934a9d4b250a0b417af1ec47bc2d0ceb6
> Author: Pedro Alves <palves@redhat.com>
> Date: Thu May 29 19:58:57 2014 +0100
>
> enable target async by default; separate MI and target notions of async
>
> CFLAGS=-g ./configure --without-guile --with-separate-debug-dir=/usr/lib/debug;make;cd gdb/testsuite;make site.exp;i=0;while runtest gdb.base/annota1.exp;! grep 'called with no handler' gdb.log ;do i=$[$i+1];echo -----------$i;done
>
> Starting program: .../gdb/testsuite/gdb.base/annota1 ^M
> warning: section not found in /usr/lib/debug/lib/modules/3.16.3-200.fc20.x86_64/vdso/vdso64.so.debug^M
> [...]
> FAIL: gdb.base/annota1.exp: run until main breakpoint (timeout)
> [...]
> readline: readline_callback_read_char() called with no handler!^M
> ERROR: Process no longer exists

Thanks for the reproducer. After investigation with a lot of head
scratching staring at hacked in logs in select place, in the end this
turned out to be real simple to trigger. All it takes is turning on
annotations, do "c", and type something while the program is running...

I've filed PR 17472 for this. I'll send a series fixing this and a
couple other terminal/readline issues shortly.

Thanks,
Pedro Alves