Re: [Valgrind-users] helgrind and stlport

[Konstantin S. <kon...@gm...>]

Hmmm.
Another wild guess: maybe you use vector::swap, which swaps internal
pointers...
If properly synchronized, it is safe, but Helgrind-unfriendly.

(A small test will help so much!!)

Julian, when we print
Location 0xB843010 is 432 bytes inside a block of size 512 alloc'd
   at 0x4023099: operator new(unsigned) (vg_replace_malloc.c:224)
   by 0x5AD3BA9: _STL::__stl_new(unsigned) (_new.h:86)
   ...

can we also print the thread and the segment where it happened?

--kcc



On Fri, Mar 28, 2008 at 3:29 PM, Vojtech Fried <voj...@se...> wrote:
> > The class std::vector<> of the STL (and most likely _STL::vector<> in
>  > STLPort too) uses a custom memory allocator. This is well explained in
>  > every book about C++ in general or the STL in particular.
>
>  We use STLPort configured with "_STLP_USE_NEWALLOC", which means that the
>  allocator should not use memory pools and stuff like that. At least I think so.
>
>  Vojtech
>
>
>
>
>
>
>  -------------------------------------------------------------------------
>  Check out the new SourceForge.net Marketplace.
>  It's the best place to buy or sell services for
>  just about anything Open Source.
>  http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>  _______________________________________________
>  Valgrind-users mailing list
>  Val...@li...
>  https://lists.sourceforge.net/lists/listinfo/valgrind-users
>