This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: mt_allocator (rev 1.28) has static initilization problems?


Brad Spencer wrote:

Unfortunately, I don't have much news; I've been pulled in other
directions by other work.

I see... Anyway, before discussing more technical details, my mistake of earlier today make me think, about *your* issue:

> Example gdb output from a run of the second program linked against the
> debug libstdc++:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0804961d in __gnu_cxx::__mt_alloc<int*>::deallocate
> (this=0xbffff5a0, __p=0x8061c68, __n=8) at mt_allocator.h:461
> 461 __block->_M_next = __bin._M_first[0];

If, the problem really is that the _S_options are not initialized and
stuck at zero, why line 461 is ever reached? Deallocate should have
returned *much* earlier!

Paolo.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]