Subject: Re: bin/9665: vi coredumps writing file after invokation with -r
To: None <email@example.com>
From: John Hawkinson <jhawk@MIT.EDU>
Date: 03/23/2000 12:07:56
In message <firstname.lastname@example.org>, email@example.com writes:
>John Hawkinson wrote:
>> After receipt of mail reminding me, invoking "vi -r db_interface.c"
>>brings up my in-progress edit of the above. Attempting to write it to
>>a file (:w dbsnap) yields a vi core dump. This seems 100% reproducible
>>and I built a vi with symbols. Here's the stack:
>Can you reproduce this problem with nvi 1.79 (last time I looked,
>NetBSD was shipping 1.66 whereas 1.79 is out since 1996).
Yes, it core dumps in the same place.
*unfortunately* during the process of debugging this morning something
managed to eat the recover file, and it turned out that I had screwed
up backing it up and had only saved the file with the email message
(metadata) rather than the actual recover file.
I'm not sure how to recreate a recover file that causes this problem,
though; trivially HUPping vi while editting db_interface.c produced
a recover file which worked just fine.