On Fri, 16 Feb 2001 [log in to unmask] wrote:
>
> Of course, it *could* be crashing due to a bug. ;)
>
> The trick here is to catch several coredumps, and see if it's crashing
> at the same stack traceback each time (indicating a bug) or if it's
> blowing up very randomly (indicating something external, or a memory-overlay
> bug that causes problems way down the line).

We have a fair number of lsv core dumps here on a system with 2GB of RAM
and lsv having very high limits for all ulim settings. My observation is
that these core dumps occur during Listserv's automatic reindexing
process.