> (gdb) where
> #0  0x2817972a in ?? ()
> #1  0x281858e3 in ?? ()
> #2  0x8057660 in LSV_sprintf ()
> #3  0x80c0434 in LSWSETEP ()
> #4  0x804fdfd in LSWCMDCL ()
> #5  0x8072c8c in LSWCMD ()
> #6  0x8096c6b in LSWJCMD ()
> #7  0x80bad22 in LSWRDR ()
> #8  0x80b4f91 in Process ()
> #9  0x80b5918 in LSWPRFGO ()
> #10 0x80600d2 in Go ()
> #11 0x8060123 in main ()

Unix core dumps are almost always due to insufficient virtual memory
quotas (either the quotas themselves or something that needs to be
increased in order to allow quotas to be actually increased, for instance
swap space or kernel parameters), but in the present case I think it
could be something else. There ought to be a SET command at the
tail of the log when this happens, and it ought to crash the server
whenever issued. Perhaps the list in question is corrupted.

  Eric