On 27. Feb 2012, at 7:42, cpapado [via Software] wrote: > The command handler on the QT app side triggers normally then calls > serveRequest(uRequestId, uInitDataId). And then, depending on whether I am > running in release mode or relwithdebinfo mode, it either crashes or > deadlocks inside serveRequest at the spin lock.
This code is called in countless other places inside an Equalizer app, it's the standard pattern we use for synchronous RMI. Does the same code work within a project (eq eqPly) in the Equalizer solution? I suspect your project settings somehow don't match. *If* you're really blocked when entering thin mutex, then somebody else should still hold the mutex, which from the code seems impossible. What's the state of _mutex? Anything but 0 means somebody has it. Can you run the lock unit test? Cheers, Stefan. -- View this message in context: http://software.1713.n2.nabble.com/Affecting-Collage-objects-outside-an-Equalizer-application-tp7301888p7321100.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
