Re: [Nano-devel] Nano 1.3.8 and 1.3.8-cvs crashes on suse 9.3 x86_64

[David Lawrence Ramsey]

Simon Strandman wrote:

> David Lawrence Ramsey skrev:
>>
>> Thanks for the report and the link, in any case.  How does current
>> CVS behave?  I imagine that renumbering won't be done properly in all
>> cases due to the above problem, but at least it shouldn't segfault.
>
> It still segfaults. :( This is the new bt:

<snip>

Okay.  I should have guessed that it wouldn't be that simple.  If it's
crashing inside malloc(), that usually means that there's a memory
corruption problem somewhere, but I can't find anything obviously wrong
on my end.

Valgrind should be able to show where any corruption is occurring,
though.  (I suppose it's lucky that a version with x86_64 support came
out last week.)  What output does "valgrind -v [path-to-nano]" produce,
assuming you're using valgrind 3.0.0, when you search and get the
segfault?  Thanks in advance.