bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: Bug#79091: info: "info --vi-keys libc:exit" causes s


From: Eli Zaretskii
Subject: Re: address@hidden: Bug#79091: info: "info --vi-keys libc:exit" causes segfault when you hit 'h']
Date: Sat, 09 Dec 2000 10:50:27 +0200

> Date: Fri, 08 Dec 2000 20:15:19 -0700
> From: Adam Olsen <address@hidden>
> > 
> > I cannot reproduce this on my machine.  Could you please send a
> > backtrace printed by a debugger given the core file, or when you run
> > Info inside a debugger to begin with?  Thanks.
> 
> (gdb) bt
> #0  0x400cd3d8 in free () from /lib/libc.so.6
> #1  0x400cd2c3 in free () from /lib/libc.so.6
> #2  0x8050eb3 in strcpy ()
> #3  0x80506c6 in strcpy ()
> #4  0x8050816 in strcpy ()
> #5  0x80508c3 in strcpy ()
> #6  0x805c490 in strcpy ()
> #7  0x80564bf in strcpy ()
> #8  0x80563d7 in strcpy ()
> #9  0x8056326 in strcpy ()
> #10 0x804fa78 in strcpy ()
> #11 0x40079cfc in __libc_start_main () from /lib/libc.so.6
> (gdb) 

Thanks.

However, this backtrace doesn't make any sense to me: it seems to
indicate that the program crashes somewhere in the library startup
code, before the `main' function was ever called.  That contradicts
the description (above) where you say that it crashed when you pressed
`h' after starting Info.

I also doubt that `strcpy' calls `free' in any reasonable library.
Hmm.  It's possible that the offending code, wherever it is, smashed
the stack somehow.

I will try to look into this, but if someone can reproduce this
problem and send more information about where it crashes, I'd
appreciate that.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]