Erik Hofman wrote: > Is is certain that reftag is set in this case? Yes. The modification to opTop is a pop, the stack contents have already been pushed at that point. I just scanned through the loop again, and don't see anywhere that an object gets copied onto the stack incorrectly -- the only way it's done is to copy the whole naRef at once, which copies the reftag also.
Even a garbage collection wouldn't cause this behavior, as it would clean up the pointed-to object and not the reference on the stack. Note, by the way, that reftag is not guaranteed to be present -- if the naRef is a number, you will see the (non-NaN) top half of the double instead. The behavior you are seeing is consistent with a number being stored in the local variable hash in the slot where you used to see an object. No idea why that might happen either. Andy _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
