Hi David, I was considering moving from VS 2005 to VS 2003, but using VS6 sounds drastic. I don't have that installed anywhere any more, and the C compiler has gotten much more correct since then. If anything, the more recent compilers should be improvements. The kinds of errors I see cause signal 11 (sigsegv) or heap corruption messages. Random hard failures are typical of heap corruption.
Is it possible that you (and I) are linking against any code that was compiled in Cygwin and, therefore, uses stdcall convention instead of cdecl? I'm reaching for this one. I see that dxlite.lib and dxexec.lib were linked against the dll version of the Microsoft C runtime, so they aren't using Cygwin. Because DXLite.lib and DXExec.lib are linked to the import stubs for the dll C runtime, I think I can use the memory-debugging features of the debug runtime to help establish when things go south. Thanks, Drew -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thompson Sent: Wednesday, December 14, 2005 4:16 PM To: opendx2-dev@lists.berlios.de Subject: Re: [opendx-dev] problem compiling import module under Windows Drew, I haven't seen anything like this. I did just recompile yesterday the entire tree with VS 2003 and used vc7, and couldn't produce a runnable version of DX. Have you tried compiling with just VS6 based tools? David
