[AGENT++] Agent++ Thread Safety

[Frank Fock]

Hi Megan,

You are probably on the wrong track here. The AVL
trees should not be modified in the AGENT++ code
concurrently anywhere.

Such modifications have to be protected by

mib->lock_mib();
..some code modifying mib registration (AVL tree)..
mib->unlock_mib();

or

mib->lock_mib();
table->start_synch();
..some code modifying table content..
table->end_synch();
mib->unlock();

Best regards,
Frank

Megan Smith wrote:
> Hi,
> 
> I posted this a few weeks ago and haven't heard any response yet.  We are
> using agent++ and have been experiencing segmentation faults from some
> corrupted memory in the mib tables during highly multi-threaded runs.  After
> running debugging utilities it appears that there are some static variables
> in the avl_map.cpp file that I can't find proper locks for anywhere.  Am I
> missing something?
> 
> Thank you for your help,
> Megan
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com