------- Comment #3 from pcarlini at suse dot de 2005-11-15 12:02 -------
> 2- Otherwise, a lock in _M_reclaim_block only when __block->_M_thread_id !=
> __thread_id. At the same time has to be changed _M_reserve_block too,
> however, and it's tricky to do that without locking at every single
> allocation: maybe, changing slightly the algorithm, an entire pool of
> blocks can be marked as used when obtained from operator new or the
> global list (at the beginning of _M_reserve_block).
Hi again. I mean to draft a version of this fix. Can you test it together
with the application which leads to SIGSEGVs? I don't think I have ready at
hand a testcase really stressing the allocator for this issue...
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24469
