On Wed, 31 Oct 2001, Justin C. Darby wrote: > Ok, since I love making myself look like an idiot, and this took me and 3 > other people to figure out, what happened was, I forgot a malloc call for > a custom typedef'd struct pointer. But, the problem was damn near > impossible to track down with the available debugging tools. Go figure.
If malloc or free segfault (and you didn't really run out of RAM), it's almost always heap corruption caused by exactly this sort of thing. Free tools like Electric Fence and commercial tools like Purify are invaluable for sniffing these things out. Glad you found it. :) --Cliff -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA
