Regarding thread safety, if threads are concurrently reading, inserting, and erasing entries in a multi-index container do you have to lockguard all of these operations or can you get away with just lockguarding the inserts and the deletes? Thanks, Allen. -----Message d'origine----- De : boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de JOAQUIN LOPEZ MU?Z Envoyé : mercredi 10 mai 2006 23:36 À : boost-users@lists.boost.org Objet : Re: [Boost-users] [multi_index] Core dump in multi-index library !! Oh, oh. multi_index_container is *not* thread safe, so this smells like the problem --and it is not, it certainly has the potential to crash your app sooner or later. Please take into account thread unsafety extends to every member function of multi_index_container, so you'd better lockguard *every* public method of Procedure_Pool. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo