I'm allocating objects with class_createInstance(), storing them on a stack (well, just a plain NSArray), and popping them off at a later time. When I pop an object from the stack, it gets released (as I expect), but I get a segfault from -[NSObject dealloc] that I can't track down.
I'm pretty sure I'm not double-releasing the object since I've sprinkled printf statements in my dealloc methods, and I've tried looking through NSObject.m to find the culprit, but can't see where the segfault is coming from (the inline functions hinder debugging somewhat). What kind of things can cause segfaults in -[NSObject dealloc]? Could this be a GNUstep bug?