A complicating sideeffect on win64 is that executables(/dlls ?) can be
called from within the WOW32 context.
So multiply your story with WOW/nonWOW and we have more places where it
can go wrong.
AFAIK, it's not possible for a 64 bit binary to load 32 bit code. The two
worlds are isolated (they even see different things for the
same registry key, for example): In fact, on win64 they provide a 64 bit and
a 32 bit Internet Explorer, since 32 bit plugins (like
Flash) cannot be loaded in Internet Explorer - 64 bits.
See also
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/running_32_bit_applications.asp
quote:
"However, 32-bit processes cannot load 64-bit DLLs, and 64-bit processes
cannot load 32-bit DLLs.".
In fact from windbg I saw only 64 bits dll being loaded.
One doesn't have to care of WOW as long as he doesn't debug a 32 bit process
under 64 bit windows (but the debugger can be
configured to not stop in WOW code - at least windbg).
So I think that, in our case, we are pure 64 bit.
And still it can be something wrong in win64 or wrong in our code. I'll
see if I can (cross)build a 64 bit exe with MSVC here.
Or anyone else having access to MSVC and a win64 machine.
Marc
bye,
Giulio
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
