Re: [Boost-users] [multi_index] SIGABRT inmulti_index_containerconstructor

From: JOAQUIN LOPEZ MU?Z (joaquin_at_[hidden])
Date: 2007-02-25 06:52:41

Hello Manual, thank you for not abandoning this
problem!

----- Mensaje original -----
De: Manuel Jung <gzahl_at_[hidden]>
Fecha: Domingo, Febrero 25, 2007 11:43 am
Asunto: Re: [Boost-users] [multi_index] SIGABRT in
multi_index_container constructor
Para: boost-users_at_[hidden]

> Hi,
> 
> After a working version with std::queue's im now back to
> multi_index_container. And new try new idea! I found out something:
> 
> This "#define" block
> -------cut--------
> #if !defined(NDEBUG)
> #define BOOST_MULTI_INDEX_ENABLE_INVARIANT_CHECKING
> #define BOOST_MULTI_INDEX_ENABLE_SAFE_MODE
> #endif
> -------cut--------
> was before all my #include's up to now. And if the "SAFE_MODE" was 
> enabled i was getting SEGFAULTs. But now i dropped this blocked
> after all my includes in the header file or even in the main
> implemantation file and dont get the errors anymore!
> 
> I hope this helps/makes any sense to you?

It does make sense, but it doesn't provide much info:
those macros have to be defined before inclusion of B.MI
headers to take effect, so that having them after the includes
is entirely equivalent to not defining them :(

Can you (I mean, are you allowed to) provide a sketch of
the class where the offending queue class is being used?
I remember you said it's a member of a more complex class,
or something like that.

Thank you,

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo