[eq-dev] Server::useConfig segmentation fault in 0.6 RC1

[Juan Hernando]

Hi Stefan,
>> Recently I've started porting and MPK based application to Equalizer.
> 
> Ola! You're the first one I am aware of being on the same path as me. :)
> 
> What kind of application is this? Where we in contact during MPK  
> 'times'?
No, we weren't in contact, I'm pretty new to the visualization niche.
I did an OSG 1.2 application to visualize detailed cortical neurons 
simulations and then adapted it to MPK. At that time (end of 2006) MPK 
was almost dead, but it was the only thing available for framebuffer 
compositing on multi-pipe systems.
Now we are moving to a cluster and it was a nice surprise to find out 
that the experience in MPK could be useful for some other library, in 
the beginning I was considering ParaComp and it looked very low level.

>> I've written a small test, which now is working. However it was  
>> crashing in the beginning and after some debugging I've come across  
>> something that, to me, seems to be a bug in Server::useConfig.  
>> Analyzing the code I've found that there is a difference between  
>> chooseConfig and useConfig in the sequence of operations performed  
>> in the server, while the first one calls Server::addConfig for the  
>> default config at some moment, the latter doesn't.
>> After the following change in Server::_cmdUseConfig:
>>    EQINFO << "Using config: " << endl << Global::instance() <<  
>> config << endl;
>>    config->setApplicationNetNode( node );
>>    +addConfig( config );
>>    mapConfig( config );
>> the test application works.
> 
> It is intentional that there is no addConfig(). Active configs are in  
> _appConfigs, and it's added to this. The bug was something else, but  
> it's fixed in the trunk now:
> http://equalizer.svn.sourceforge.net/equalizer/?rev=2405&view=rev
I'll take a look, thank you very much for the fix.

Regards,
Juan