[Insight-developers] ITK 4.2.1: ITK_AUTOLOAD mechanism again

[Wenzel, Fabian]

Hi all,

The autoload mechanism of ITK in 4.2.1. is causing me a lot of headaches in recent days.

I have included the patch Bradley released a few weeks ago (since the autoload mechanism was completely broken).

There are two observations which I do not understand:

* If multiple files of an application intend to read itk images and include <itkFileReader.hxx>, the static factory mechanism is actually invoked a number of times and the built-in IO modules (jpg/gdcm/nifti/...) are present multiple times in the object factory list. Is this intended?

* Whereas the issue above is more or less harmless (it will just produce some overhead), I cannot get my IO-plugin work as expected (MSVC9, x64). My application scenario is

python -> python C-extension -> customDLL (that reads via ITK) -> ITK -> (autoLoad) myIO-plugin

I have checked that everything is built for x64 and uses consistent MSVC Runtime Libraries.

The problem is that even though "myImageIO" is created correctly in itkImageFileReader.hxx, image information (direction, spacing etc.) is not correct after the call to ReadimageInformation() (line 152). While debugging, I found out that the "this" pointer in the "ReadImageInformation() method" differs from m_imageIO.m_pointer, so the backend routine reads image information to uncorrect memory.

Is there anyone who might have an explanation why a "this" pointer might be different during a function call without changing it explicitely? (Or is the Visual Studio 2008 debugger broken?)

Best regards,

        Fabian



________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.