Bug#1897: apropos not resilient to index.db corruption

1995-11-25 Thread Bill Mitchell
Alvar Bray: I have heard several other people say they have had corrupt database files - how do they get corrupted? I have never managed to corrupt mine (but then I, as the package maintainer, wouldnt would I) Possibly a SIGINT, SIGQUIT, SIGTERM, SIGKILL at an inopportune time.

Bug#1897: apropos not resilient to index.db corruption

1995-11-25 Thread Raul Miller
Alvar Bray: I have heard several other people say they have had corrupt database files - how do they get corrupted? I have never managed to corrupt mine (but then I, as the package maintainer, wouldnt would I) I imagine one technique might be to have the file system get full during a d

Bug#1897: apropos not resilient to index.db corruption

1995-11-25 Thread Austin Donnelly
On Sat, 25 Nov 1995, Alvar Bray wrote: [...] > > I have heard several other people say they have had corrupt database > files - how do they get corrupted? I have never managed to corrupt > mine (but then I, as the package maintainer, wouldnt would I) I have no idea how mine got corrupted, sorry :

Bug#1897: apropos not resilient to index.db corruption

1995-11-25 Thread Alvar Bray
Hi Austin, > Package: man > Version: 2.3.10-2 > > 'man -k' and 'apropos' with a damaged or corrupted index.db > segfaults. This is not a very friendly error message. > > I have traced the problem to the following piece of code: > ... > > Could this infelicity be passed on to the upstream mainta

Bug#1897: apropos not resilient to index.db corruption

1995-11-25 Thread Austin Donnelly
Package: man Version: 2.3.10-2 'man -k' and 'apropos' with a damaged or corrupted index.db segfaults. This is not a very friendly error message. I have traced the problem to the following piece of code: whatis.c 364: /* scan for the