Re: [xml] libxml causes crash on windows

[Jellinghaus Andreas <Andreas Jellinghaus winter-ag de>]

Hi Bjoern,

thanks for your help!

The crash I saw was the typical access to a random memory location outside the processes memory.

Thanks for reminding me on the VSCRT incompatibilities issues.
Now I recompiled libxml myself with VS2008 (libxml 2.7.8 with small editing of win32/Makefile.msc
- some extra "+" at the start of three new lines), and tried again with that.

It works now, said app with my dll and the new compiled libxml works now fine - in release mode.

If I compile my dll in debug mode, the dll isn't even loaded - R6034. If I link my debug dll
with libxml_a.lib instead, it works, but the 3rd party app again crashes. So I guess I need
to recompile libxml once as a debug binary and once as a release binary and always use the
right dll?

I had a look with dependency walker at the 3rd party app, and the dll's listed directly are:
mfc42.dll msvcrt.dll kernel32.dll user32.dll advapi32.dll wsock32.dll
msvcp60.dll version.dll

does anyone know what version of VS and what flags to use with compiler and linker might work
best with those files? if I googled right, mfc42.dll is Visual C++ 4.2 from 1998.

I can't even compile other libraries such as openssl with vs 2005, and guess they won't work
with such an old visual c++ either - in case I can find that somewhere.

Maybe I need to try static linking my dll with libxml, openssl and maybe even the windows
system libs to mitigate the problem?

does anyone have experience with this type of DLL hell on windows?

Regards, Andreas
p.s. I don't have the typical dll hell issues - I don't copy msvcrt* files around, but rather
use the proper vcredist files, and for libxml, openssl etc. I have one seperate directory
with the third party app and all those dll files, so that app uses those files in that
directory, and the rest of the system stays clean.