Debian bug report logs - #702
locate crash with large db

Message received at debian-bugs:

From tinny.eis.net.au!ernie Sun Apr  2 04:17:50 1995
Return-Path: <ernie@tinny.eis.net.au>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0rvNfC-0002CgC; Sun, 2 Apr 95 04:17 PDT
Received: from tinny.eis.net.au ([203.12.171.1]) by pixar.com with SMTP id AA00223
  (5.65c/IDA-1.4.4 for <debian-bugs@pixar.com>); Sun, 2 Apr 1995 04:17:26 -0700
Received: (from ernie@localhost) by tinny.eis.net.au (8.6.10/8.6.9) id VAA06202 for debian-bugs@pixar.com; Sun, 2 Apr 1995 21:16:45 +1000
From: Ernie Elu <ernie@tinny.eis.net.au>
Message-Id: <199504021116.VAA06202@tinny.eis.net.au>
Subject: locate crash with large db
To: debian-bugs@pixar.com
Date: Sun, 2 Apr 1995 21:16:44 +1000 (EST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 1005      

My first bug report so it may me a bit rough.

The problem in a nutshell is that locate <filename> crashes with a
Segmentation Fault when the loacate database is quite large, mine is over
500k. The problem does not occur if you run updatedb --old-format on the
same system. The problem also does not occur if I unmount a couple of drives
and run updatedb (no flags) again, thus producing a smaller database.

I have tried this on 2 systems that have about 2gb of data (news servers)
and the both do it "out of the box". My work around has been to patch the
/etc/cron.daily/find script to include the --old-format flag for updatedb.


I am running:-

Debian 0.93R5

kernel 1.2.1 as shipped
libc.so.4.6.26


All are fresh installs yesterday.


- Ernie.
_____________________________________________________________________
        EISnet - ernie@tinny.eis.net.au -  Brisbane - Australia
                       "I ping, therefore I am." 
_____________________________________________________________________

Your message didn't have a Package: line at the start (in the pseudo-header following the real mail header), or didn't have a psuedo-header at all.

This makes it much harder for us to categorise and deal with your problem report; please ensure that you say which package(s) and version(s) the problem is with next time. Some time in the future the problem reports system may start rejecting such messages.

Full text available.