[Dcmlib] building with shared libs

[Mathieu Malaterre]

Hi Greg,

  The fact that it is working is not a guarantee there is not an
issue. Can your reproduce the problem with multiple DICOM files, or
just one ?
  If just one, please send me a copy of it (private email).

Thanks
-Mathieu

On Mon, Sep 8, 2008 at 1:00 AM, Greg Book <gbook at gbook.org> wrote:
> I've successfully built and used gdcm without shared libs, but am having
> trouble getting it to work with shared libs on windows. It builds ok and I
> can link it ok with my program, but when I run it... it fails when trying to
> open a dicom image.
>
> CMake was configured with:
> build shared libs: on
> build examples: off
> build testing: off
> build applications: off
> documentation: off
> use itk: off
> use vtk: off
> wrap python: off
> For VC++ 2005
>
> When running the program in debug, this is the error I get when breaking:
> "Unhandled exception at 0x7c91b1fa in MIView.exe: 0xC0000005: Access
> violation writing location 0x00000010."
>
> The call stack is as follows:
>      ntdll.dll!7c91b1fa()
>      [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
>      msvcp80d.dll!std::basic_filebuf<char,std::char_traits<char>
>>::_Endwrite()  Line 553 + 0x16 bytes    C++
>     msvcp80d.dll!std::basic_ifstream<char,std::char_traits<char> >::close()
> Line 700 + 0xb bytes    C++
>      gdcmDSED.dll!10055cbb()
>      gdcmMSFF.dll!00eb571c()
>
>
> I'm wondering if the problem is in the gdcmDSED and gdcmMSFF DLLs? It worked
> fine when linking regular .lib files, but not for dlls, which is
> surprising...
>
> -Greg
>
> _______________________________________________
> Dcmlib mailing list
> Dcmlib at creatis.insa-lyon.fr
> http://www.creatis.insa-lyon.fr/mailman/listinfo/dcmlib
>



-- 
Mathieu