On 5. May 2014, at 10:01, "cpapado [via Software]" 
<[email protected]> wrote:

> Personal preference + an exercise in getting familiar with Collage. 

Good reason. :)

> Judging from the source, it shouldn't be too hard. However, I'm stuck right 
> now with Collage blowing up on the Receiver thread, after it dispatches to 
> object command to the handler function. EXC_BAD_ACCESS  with the following 
> stack trace: 
> 
> rame #0: 0x0000000104b069d0 
>     frame #1: 0x00000001003b7db8 
> libCollage.110.dylib`co::Dispatcher::dispatchCommand(co::ICommand&) + 104 
>     frame #2: 0x00000001003f30bc 
> libCollage.110.dylib`co::ObjectStore::dispatchObjectCommand(co::ICommand&) + 
> 300 
>     frame #3: 0x00000001003d0d29 
> libCollage.110.dylib`co::LocalNode::dispatchCommand(co::ICommand&) + 57 
>     frame #4: 0x000000010048da50 
> libEqualizerFabric.172.dylib`eq::fabric::Client::dispatchCommand(co::ICommand&)
>  + 128 
>     frame #5: 0x00000001003d0bca 
> libCollage.110.dylib`co::LocalNode::_dispatchCommand(co::ICommand&) + 26 
>     frame #6: 0x00000001003cf674 
> libCollage.110.dylib`co::LocalNode::_handleData() + 596 
>     frame #7: 0x00000001003cdef0 
> libCollage.110.dylib`co::LocalNode::_runReceiverThread() + 320 
>     frame #8: 0x0000000100366c32 
> libLunchbox.190.dylib`lunchbox::Thread::_runChild() + 738 
>     frame #9: 0x0000000100366949 
> libLunchbox.190.dylib`lunchbox::Thread::runChild(void*) + 9 
>     frame #10: 0x00007fff8cdba899 libsystem_pthread.dylib`_pthread_body + 138 
>     frame #11: 0x00007fff8cdba72a libsystem_pthread.dylib`_pthread_start + 
> 137 
> 
> This happens with and without specifying a custom handler for that particular 
> command...What is weirded is that the handler itself executes fine (and I 
> verified the relevant pointers as well), the exception happens when getting 
> back into the dispatchCommand function. I gotta investigate more but it's 
> 4:00am here in the US and its time to sleep :). If you have any suggestions, 
> I'd appreciate them! 

Not really. From what you describe it looks like your stack gets corrupted, but 
I can't say why. I guess the customCommands unit test executes fine? Does it 
also crash if you do nothing in your command handler?

> Yup :). One of our software stacks is EQ-based with different renderers on 
> top. Here's an early photo 
> http://labs.cs.sunysb.edu/labs/images/reality/applications/GIS.JPG of one of 
> our GIS renderers that runs on top of EQ. 

Nice - I'ld like to hear more about your experiences at some point. Maybe we'll 
run across each other at a conference.


Cheers,

Stefan.



signature.asc (858 bytes) 
<http://software.1713.n2.nabble.com/attachment/7585445/0/signature.asc>




--
View this message in context: 
http://software.1713.n2.nabble.com/Communicating-information-FROM-the-rendering-code-to-the-application-logic-tp7585385p7585445.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

Reply via email to