Leeuw van der, Tim wrote: > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] on behalf of John Machin > > Sent: Thu 2/3/2005 12:00 PM > > To: python-list@python.org > > Subject: Re: Crashing Python interpreter! (windows XP, python2.3.4, 2.3.5rc1,2.4.0) > > > > > > Leeuw van der, Tim wrote: > > > > > >> > Do you have a file called drwtsn32.log anywhere on your computer? > > > > > > No, unfortunately I cannot find such file anywhere on my computer.... > > > > > > What do I do to get such file? Or anything equally useful? > > > > > > > On my Windows 2000 box, just crash something :-) > > > > > > Perhaps this may help: > > > > http://www.windowsnetworking.com/kbase/WindowsTips/Windows2000/RegistryTips/RegistryTools/DrWatson.html > > > > Using this URL, I found the log file and it's about 1Gb big...
Yeah, well, it's a *LOG* file -- unless you fiddle with the registry settings (not recommended), you get one lot of guff per crash. But 1 Gb???? > I'll have to find out what is the useful part of it (or remove it and crash again). The useful part would be the tail of the file. Remove it? It may contain evidence useful for other problems (that you didn't know you were having). Try rename. > I don't know why searching all drives using windows 'search' did not find the file! Possibilities: 1. You have a virus that renames the drwtsn32.log file for the duration of a search. 2. Emanations from UFOs are affecting computer circuitry in your neighbourhood. 3. Microsoft programmers stuffed up. 4. You had a typo. > > When I have a usefull crashdump, what should I do? Attach to e-mail and post it here? You could eyeball it to see if it gave you a clue first. Failing that, just post a copy of the part(s) from just ONE crash that look something like this: *----> Stack Back Trace <----* FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name 0012D6F8 77F8819B 7803A700 7C34F639 7803A730 7C36B42C ntdll!RtlpWaitForCriticalSection 0012D73C 1E0A73CE 7803A710 00000000 00AE0900 00000000 ntdll!ZwCreateThread 7C36C576 E87C3822 FFFD5D89 E80C75FF FFFE3081 FC658359 !PyTime_DoubleToTimet B8680C6A 00000000 00000000 00000000 00000000 00000000 <nosymbols> > Should I include the user.dmp file too? Look at it; how big is it? [my latest is 13MB for @#$% sake] Is it in ascii or binary? Does it look useful? What proportion of people who get this newsgroup/mailing-list via *E-MAIL* will be overjoyed to receive it? Are you sure you will not be splattering company-confidential data all over the Internet? > > Should I do the same for both python 2.3.5r1 and python 2.4? Or is it sufficient to do so for Python 2.4? If you are sending only stack back trace snippets as above, then send both just in case they are different. -- http://mail.python.org/mailman/listinfo/python-list
