Am 15.09.2010 22:54, schrieb Dan Halbert:
I am still trying to track down the source of an R6034 error when an
pyinstaller-generated executable runs. I have created a simple test
program (a bunch of imports) that builds an identical installation
directory with the same set of pyd, dll, and manifest files, but it
does not generate an R6034.
Interestingly (?), my execitable continues and runs fine after I
click through the R6034 dialog box.
So it is not the exact same error that we all "know and love" ;) where
the executable doesn't run at all. Hmm. Is there any minimal test case
that I could try?
The R6034 occurs well after a bunch of python code runs. Do you have
any suggestions about tracing the execution so I can see exactly
which load is causing the R6034? I tried ProcessMonitor, looking for
missing DLL's, but didn't really get anywhere. I am not sure the
python trace module would help, because I don't see how to trace to
the point of the R6034 dialog box, but not after. Something like an
strace for Windows might help - I'm not sure.
Googling 'strace windows' brought up this:
http://www.intellectualheaven.com/default.asp?BH=projects&H=strace.htm
No idea if it works though, haven't tried it.
Regards
--
Florian Höch
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
