Re: [Lynx-dev] lynx: double free or corruption (fasttop)

[Frédéric L . W . Meunier]

On Fri, 29 Oct 2010, Thomas Dickey wrote:

> On Fri, 29 Oct 2010, Fr?d?ric L. W. Meunier wrote:
>
> >  Is this supposed to be a bug in lynx or glibc ? I get it randomly while
> >  removing a file with 'r'.
>
> valgrind might show the problem (but running with valgrind is slow).
>
> >  How would one track it down ? gdb bt didn't return anything.
>
> No stack at all?
>
> lynx normally catches core dumps, but
> lynx does have an option to dump core (settable at runtime).
> gdb might make some use of that.

When it crashes, returns something along those lines. lynx is compiled 
with -g.

#0  0xb7766424 in __kernel_vsyscall ()
#1  0xb75e7b71 in raise () from /lib/libc.so.6
#2  0xb75e9533 in abort () from /lib/libc.so.6
#3  0xbfaf9d20 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

I noticed it also happens with 'm', renaming a file. But with 'c', I 
could create various files and nothing happened.