[ITK] Win64 Visual Studio 12 segfaults

[Lowekamp, Bradley (NIH/NLM/LHC) [C]]

The info I read about an SEH exception was here:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms680657(v=vs.85).aspx

I believe that google test tries to handle these things in the test driver to help recover from things that are recoverable. That is why it's different than expected with the ITK test driver. It sounds to me like they are in the same category with some invalid memory access and miss aligned SSE data.

As this only happening with the VS12 64-bits, and 32-bits is OK, I'm blaming the compiler and hoping your patch fixed it :)

Thanks,
Brad

________________________________________
From: Niels Dekker [niels-xtk at xs4all.nl]
Sent: Friday, January 30, 2015 6:13 AM
To: community at itk.org
Subject: Re: [ITK] Win64 Visual Studio 12 segfaults

Hi Bradley,

I googled as well, but found no relation so far between the SimpleITK SEH
exceptions and the Win64 VS12 access violation compiler bug we've been
discussing. Could the SimpleITK/VS12 problem be related to the following?
http://stackoverflow.com/questions/15953255/seh-exception-when-using-googlemock

Xu Chang answered on Dec 10, 2014, at the Stackoverflow page:
> After a lot of try, I found the reason is:
>
> You have to compile the gmock and your project in the same configuration!
>
> That means you have to compile the gmock in DEBUG(RELEASE) configuration,
> if you want to link it in the DEBUG(RELEASE) mode. If not, the
>
> unknown file: error: SEH exception with code 0xc0000005 thrown in the
test body.
>
> always occurs.

Does that Stackoverflow answer seem helpful to you?  I have to admit, I'm
not familiar with this stuff, but can you check the gmock configuration
for VS12 Win64 Release?

Kind regards, Niels

Bradley Lowekamp wrote on Jan 30, 2015:
> No just 26 of them that are deconvolution filters, not the fast
> marching/colliding fronts ones. Most of those others where fixed in today
> builds on next [1].
>
> It's quite hard to maintain all those builds, and wrappers for 7 different
> languages, please pardon the red ness. The top master/package section
> should be green except for window 64 linking issue.
>
> The BasicFilters.* failing tests are the C++ native code, and don't have
> the extra language to hide the abnormal program termination.
>
> The error reported by gtest is:
> unknown file: error: SEH exception with code 0xc0000005 thrown in the test
> body.
>
> I truthfully haven't seen that error before, and googling it looks like
> its similar to a segfault, I believe I saw some of these filters failing
> before it ITK with this compiler.
>
> I hope your patch addresses these issue too, but it could very well be one
> of the existing examples you demonstrated that is not covered by ITK
> tests.
>
> Brad


_______________________________________________
Community mailing list
Community at itk.org
http://public.kitware.com/mailman/listinfo/community