Giulio Bernardi wrote:
I'm answering both to Vincent and Marc in this mail:
To Vincent:
No luck with -gh and -dMSG_DEBUG :\.
-gh is not reliable, since after windows exceptions, a lot of access
violations
occour, so a lot of data isn't deallocated because of exceptions being
raised.
Tracing messages (or using -dTRACE) isn't very helpful either :\
To Marc:
In lazarus on win64 there is no manifest, since there are no resources
at all: IIRC windres
is used on win32 to embed resources into executables, but there is no
windres on win64. In
fact lazarus doesn't have any resource (i watched into it with CFF
Explorer - http://www.ntcore.com/exsuite.php)
so no icons, no manifests.
But your observation made me study a bit this assemblies/manifest thing
(I thought those "manifests"
were something needed to have an xp look, but they are a way more
powerful and complex thing) and
I think our problem is somewhat related to this thing.
[snip]
WOW, thanks for the analysis. This is a new area of programming for me.
I know what I've to read the coming days. :)
Now, our problem seems to be related to this activation context thing:
windbg gives me this stack trace:
Child-SP RetAddr Call Site
00000000`0006f2d0 00000000`78c444cb
ntdll!RtlActivateActivationContextUnsafeFast+0x92
00000000`0006f3a0 00000000`78c44be2 USER32!UserCallDlgProcCheckWow+0xc2
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.
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
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
