>For mysterious crashes with no explanation, it's probably due to data
>corrupted by blown stacks.
99% of all the crashes I experience leave as their final grin this error
message:
"ns_realloc: could not allocate %d bytes"
Invariably, this messages comes at a time in which I would have thought
there was still plenty of SWAP space left on the machine. The message
itself comes from aolserver/thread/ns_realloc.
What this tells me is that:
A) It would be very nice to have a forum and poll (at aolserver.com?) in
which developers/users can interact specifically about mysterious crash
issues, detail the symptoms they see and "vote" on which ones are the
most frequent.
B) I would love to see a -define DBG_MEMORY compile time option that would
help
trace down this issue and other memory/stack related issues. When
compiled
in, we could either get a trace of what modules, what pages, or what
filters or procs are triggering the call to ns_realloc, and also get a
snapshot of various structures within the system to help us understand
why realloc or Ns_ThreadRealloc failed at that time.
Thanks,
Jerry
========================================================
Jerry Asher [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
Berkeley, CA 94709 Fax: (877) 311-8688
