Re: "info --vi-keys foo" inciting a segfault in info

[Eli Zaretskii]

On Sun, 1 Apr 2001, Josip Rodin wrote:

> Eli Zaretskii wrote:
> > corruption of the malloc memory chain, and that means the bug is somewhere
> > else, not in the chain of calls shown by the backtrace.  Since I still
> > cannot reproduce the crash, it's hard to find that other pace.
> >
> > some code somewhere is corrupting the memory chain, and causes malloc/free
> > to crash in random places...
> >
> > But --vi-keys could also be not really relevant: it might be that the bug
> > is somewhere else, and only turns up with --vi-keys because the
> > additional argv[] element changes the memory-allocation pattern in the
> > libc startup code.
> 
> Has any progress been made diagnosing this bug? Just wondering...

Unfortunately, no, at least not to the best of my knowledge.

If someone can run this with Purify or Efence, perhaps the offending code 
will be easy to spot.