Hi David,
I think the problem is that dxexec.exe uses a different C runtime from
dll modules built with dxexec.lib and dxlite.lib. I used the C runtime
memory allocation hooks to see that I get crashes when AutoColor tries
to free memory allocated during MyConstruct (a Construct module
recompiled
If you figure it out, can you give me some ideas how to fix it? I'm
more than happy to try and get it all sorted out.
On a similar topic, I've got everything compiling with VS2003 (cl
v13.10.3077). Everything seems to be working pretty well, except:
Our code links with BINMODE.OBJ to turn
Hi David,
If linking with binmode.obj fails, does setting the global _fmode =
_O_BINARY still work correctly? It should do the same thing. Neither
binmode.obj nor the _fmode global are supposed to affect stdout, stderr,
and stdin. That's a definite bug. You could set the default fmode to
binary
I've been playing around with it a bit. Linking with binmode.obj
works, the problem is that stdout for some reason is writing out text
in binary. I tried using the setmode route but it doesn't change. I'm
wondering if for some reason something else is going on. Here is a
snippet of the code
