[Dune] allocators... dingleton vs. instance

[Markus Blatt]

Hi,

On Wed, Oct 03, 2012 at 02:54:54PM +0200, Christian Engwer wrote:
> 
> thanks for your opinion.
> 

your welcome.

> 
> I'm currently writing a debugging allocator for dune-common and wanted
> to make sure that I don't produce false positives. I needed an
> alternative allocator to check that the code really works with other
> allocators. There a many allocators in g++-ext but we can not rely on
> these. The second point is that I had to debug quite some
> memory-management problem in the last time. Here an additional
> memory-debugging tool would be handy. valgrind obviously works, but
> larger programs become _really_ slow.
> 

I would be interested in the answer of the original questions. Maybe
the standard commitee just failed forse such a case..

What about other existing options for memory debugging? Good old
efence comes to my mind. http://libcwd.sourceforge.net/ looks
promising, too. 

Cheers
Markus

-- 
Do you need more support with DUNE or HPC in general? 

Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de
Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany
Tel.: +49 (0) 160 97590858  Fax: +49 (0)322 1108991658