I'm trying to generate the stack trace, but since the image magick is not distributed as a debug-version I cannot give you that.
I cannot simplify the project to only have dependencies on ImageMagick (using the Magick++ demo). However most options from the Magick++ demo are used in my settings, so I really don't think this is the case. The question is still, how do I get a working debug-mode for ImageMagick? What I did: - Installed the binary dll-version including C/C++ development files - I downloaded the source code version of ImageMagick and compiled in DLL debug mode. So I still use the include-directory of the binary installer (since no include directory seem to be there in the source code version) and then link using the CORE_DB_Magick++.lib/dll and CORE_DB_magick_.lib/dll files However this issues an "unresolved external symbol "__declspec(dllimport) public: __thiscall Magick::Color::Color(unsigned char, unsigned char, unsigned char)" Do I need to put additional linker libs/dll's into the linker options, when the project is using the self compiled debug version - or is the header files of the binary installer not equivalent to the distributed source code version? (or how can I generate the header files directory of the source code distribution)? Best regards Preben Holm [email protected] skrev: >> However, the function I have problem with is the following (crashes in >> debug mode always, and release mode only sometimes): >> > > Without a stack trace we cannot help. You are calling non-ImageMagick methods > and the bug may be there. To ensure you have the right workspace settings we > recommend you compile/run the button demo program typically found here: > c:\Program Files\ImageMagick-6.5.2-Q16\Magick++_demos. Once you confirm it > builds and executes, replace the button source with your own source and run. > Does the program work now? > _______________________________________________ Magick-users mailing list [email protected] http://studio.imagemagick.org/mailman/listinfo/magick-users
