[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: user/3769: vi -r <filename> segfaults
- To: bugs_(_at_)_cvs_(_dot_)_openbsd_(_dot_)_org
- Subject: Re: user/3769: vi -r <filename> segfaults
- From: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
- Date: Wed, 5 May 2004 15:05:02 -0600 (MDT)
- Cc:
- Reply-to: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
The following reply was made to PR user/3769; it has been noted by GNATS.
From: "Todd C. Miller" <Todd_(_dot_)_Miller_(_at_)_courtesan_(_dot_)_com>
To: matthiasb_(_at_)_acm_(_dot_)_org
Cc: gnats_(_at_)_openbsd_(_dot_)_org
Subject: Re: user/3769: vi -r <filename> segfaults
Date: Wed, 05 May 2004 14:48:35 -0600
The problem is that the recovery files were in an inconsistent
(corrupted) state and so the db routines crash and burn. There's
not much that can be done about this due to vi's use of the db
routines.
It would be nice to have a way to pass the O_SYNC flag to the
underlying database but there is no way to do so. Yes, this is
very annoying.
- todd
Visit your host, monkey.org