[Insight-developers] ITK test failures in Debug only

[Mathieu Coursolle]

Hi,

I just ran ctest on a single processor (disable all others), and I got
100% of the tests
to succeed, no failures, which I think confirms its 5).

Thanks.

Mathieu



>There's also 
>
>5) Random failures on multiprocessor boxes.  I haven't checked lately but we
>used to see this all the time on our quad-core Macs.  I had hoped that the
>fix made to the locking/threadsafe code.  I noticed that a lot of the
>'not-green' machines on the dashboard are Macs.
>
>
>On 9/13/07 6:32 AM, "Luis Ibanez" <luis.ibanez at kitware.com> wrote:
>
>> 
>> Hi Mathieu,
>> 
>>     Is the Debug build a "clean" build ?
>> 
>>     I mean: Is it starting from scratch every time ?
>> 
>> 
>> The messages I see in the failing tests are mostly of the
>> two following types:
>> 
>> 
>>     a) *** Exception executing: Segmentation fault
>> 
>>     b) *** Exception executing: Illegal instruction
>> 
>> 
>> 
>> The typical suspects therefore are:
>> 
>>    1) You may have CVS updated some headers but
>>       not recompiled the corresponding libraries
>> 
>>    2) Uninitialized variables (in particular pointers)
>> 
>>    3) Byte swapping misinterpretation errors
>> 
>>    4) Outdated shared libraries getting in the way.
>>       (do you have ITK shared libraries in your path ?)
>> 
>> 
>
>