Carsten Neumann wrote: > yes, that matches my understanding as well. What I don't get anymore at > this point is why it crashes anyways. AFAICS we don't do anything wrong. > By the time osgInit runs the pointer objects should be constructed and > from the standard quote Gerrit posted, any atexit handler registered by > osgInit should then run *before* the pointer objects are destroyed. This > order of events is fine, I think. I'm confused.
I agree with your analysis here. So, I'm confused too (if it helps :) Are you able to see _when_ the materials are destroyed the first time? There's no third culprit involved? Because the objects seem to be destroyed before running osgexit(), without the ptr's being null. (Also, are the MTRefPtr's nulled in their dtor? I don't think so. Perhaps that's a good idea to avoid accessing stale objects?) Hm, I'll have to run the debugger a bit myself I think. :) Cheers, /Marcus ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
