[dune-fem] StandardArrayAllocator vs. CArrayAllocator

Robert K. robertk at ucar.edu
Wed Nov 13 18:37:25 CET 2013


On 11/13/2013 08:08 AM, Rene Milk wrote:
> On 11/13/2013 01:21 PM, Tobias Malkmus wrote:
>> On 11/13/2013 12:40 PM, Rene Milk wrote:
>>> Dear all,
>>>
>>> I've discovered that using StandardArrayAllocator as the
>>> DefaultArrayAllocator's base causes a stack corruption after
>>> DynamicVector's append/resize when my application is compiled with
>>> -fopenmp. Using CArrayAllocator this corruption does not happen. I'm
>>> wondering if a) someone else has seen an effect like this before and b)
>>> there are arguments against using CArrayAllocator.

What does valgrind say?

Rob

-- 

Dr. Robert Kloefkorn           <robertk at ucar dot edu>

Institute for Mathematics Applied to Geosciences (IMAGe)
National Center for Atmospheric Research (NCAR)

1850 Table Mesa Drive, Boulder CO 80305, USA.

Phone: +1 303 497 2481




More information about the dune-fem mailing list