[Insight-developers] ITK test failures in Debug only

[Luis Ibanez]

Hi Mathieu,

Thanks a lot for exploring this further.

Fixing this one is going to be *a lot* of fun.

I'm wondering if the failures in "mini2"
http://www.itk.org/Testing/Sites/mini2/Darwin-Xcode2.2.1-dbg/20070913-0100-Nightly/Test.html
are due to the same phenomenon.

This machine is also building for debug,

One test is seg-faulting and the other is throwing an exception:

     "terminate called after throwing
      an instance of 'std::logic_error'
       what():  H"

-----


Mathieu:

    Is this a something that started failing recently in your build ?
    or do we have reasons to believe that it has never worked ?

    If the failure appeared recently, we may get lucky by just
    looking at recent CVS commits in the Multithreader and try
    to find a suspect.



    Does your same machine builds VTK ?
    if so, do you see any similar errors in VTK ?


    The reason why I'm asking is because the ITK Multithreader
    descends from the VTK one.

    The started with the same genes, but have evolved in different
    ecological niches.

    A gvmdiff comparisson of both brings interesting "__APPLE__"
    genes that only the ITK MultiThreader has acquired.
    E.g. Lines 123-134.



If it is not too much to ask, I'll be interested in seeing if
a build of ITK 3.2 in your system brings up these same errors.
If they do not appear, at least we will have framed the problem
in a 6-months window.



    Thanks


       Luis



-----------------------
Mathieu Coursolle wrote:
> 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 ?)
>>>
>>>
>>
>>
> 
> 
>