Thanks for your helpful answer.
Zwicky, William R ERDC-CERL-IL Contractor wrote:
> Your program left something in a bad state when it exited. This didn't cause
> your program to crash while running, but when it exited, Windows detected the
> bad state and brought up Dr Watson. The bug could be anywhere.
> When I get into that kind of trouble, it's usually because I'm bending the
> rules somewhere. Are you using third-party libraries? Native code? Direct
> calls to the Windows API?
Just a few direct calls to the windows API.
> Take a closer look at the Dr Watson dump, it should contain filenames that
> tell you where it crashed. If the crash is inside a dll or pyd file, that
> should tell you where to start looking.
The DrWatson window cannot be resized and I cannot cut&paste its text it
shows anywhere else, it does mention a report file, which does not
contain anything of interest.
Does anyone ever use this junk tool for anything useful? Surely there is
a better alternative?
> The only other thing to do is disable chunks of code until it stops crashing,
> then look closely at those chunks.
I was hoping there would be a way to extract the information in a more
decisive/automated way, so I may put this issue on the backburner for
someone else with more spare time to sort out!
>> -----Original Message-----
>> From: Antoine Martin [mailto:antoine@...]
>> Sent: Friday, August 21, 2009 3:13 PM
>> To: py2exe-users@...
>> Subject: [Py2exe-users] DrWatson on exit()
>> I'm using py2exe to make a win32 installer, everything works
>> really well, except that when the program exits DrWatson pops up.
>> Basically, my code reaches the end of the main() method and
>> something happens that makes win32 unhappy... How do I find
>> out what that is?
>> I've tried using sys.exit(0) rather than just returning from
>> the main() method, no difference.
>> The information I can see from DrWatson is large and not very
>> useful at first sight.
>> I've seen quite a few posts about DrWatson, but none of them
>> seem to have any information on how to debug issues like these...
>> Apologies if this has been covered before and I have missed it.
>> Just a thought, is it possible that if another (non main)
>> thread is still running it would cause a problem like this?
>> (like a gobject timer?)
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> Py2exe-users mailing list