> Is there anyway to get this baby to generate a coredump so I can at >least post mortem it? ulimit -c unlimited That ought to allow core dumps, although it seems that you've figured that out already. As for your problem, is it reliably repeatable? Does it always crash on the same message? If so, it's certainly possible that you've got some sort of magic message that's just wacky enough to cause a memory allocation problem. If it is one particular message, and you've got port 504 open, you could log in from the BBS client and move or copy that message to a public room -- and then I could point my own copy of WebCit at your Citadel server and see if it crashes for me too. If so, it's a garden-variety memory allocation bug; if not, it's something local to your host system.
- [Citadel Development] (no subject) IGnatius T Foobar
- [Citadel Development] (no subject) fleeb
- [Citadel Development] (no subject) wizard of aahz
- [Citadel Development] (no subject) wizard of aahz
- [Citadel Development] (no subject) Monochrome
- [Citadel Development] (no subject) IGnatius T Foobar
- [Citadel Development] (no subject) Monochrome
- [Citadel Development] (no subject) Monochrome
- [Citadel Development] (no subject) shayne
- [Citadel Development] (no subject) IGnatius T Foobar
- [Citadel Development] (no subject) IGnatius T Foobar
- [Citadel Development] (no subject) IGnatius T Foobar
- [Citadel Development] (no subject) IGnatius T Foobar
- [Citadel Development] (no subject) Monochrome
- [Citadel Development] (no subject) IGnatius T Foobar
- [Citadel Development] (no subject) fleeb
- [Citadel Development] (no subject) Monochrome
- [Citadel Development] (no subject) dothebart
- [Citadel Development] (no subject) IGnatius T Foobar
- [Citadel Development] (no subject) IO ERROR
