[Insight-developers] Malloc Debug as Dynamic Coverage?

[kent williams]

I'm starting  ctest -D NightlyMemoryCheck on bloch.psychiatry.uiowa.edu,
which is a 4 core Mac Pro ;-)


On 7/8/09 12:56 PM, "kent williams" <norman-k-williams at uiowa.edu> wrote:

> Valgrind builds and runs on OS X just fine.  What it doesn't do just yet is
> work with 64-bit programs...
> 
> 
> On 7/8/09 11:29 AM, "Sean McBride" <sean at rogue-research.com> wrote:
> 
>> On 7/8/09 11:20 AM, Bradley Lowekamp said:
>> 
>>>> Some of those malloc env vars can be added with no problem.  Others
>>>> cause new output to stdout (stderr?) which some tests interpret as a
>>>> test failure (presumably because such output was not expected).
>>> 
>>> There is also variable to redirect the output of malloc to another
>>> file
>> 
>> Oh yeah, forgot about that one!
>> 
>>> so my experimental is running just fine. I have the heap
>>> checking going on, it slows down some test significantly but over all
>>> the timing of all the tests is not bad. I think its only going to take
>>> 4 times as long as a regular testing.
>> 
>> Can you share the URL when it's done running?
>> 
>>> Maybe the mac valgrind is just around the corner :)
>> 
>> I've been hoping so for years. :)
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers