Message 144847 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	santoso.wijaya
Recipients	amorilia, brian.curtin, rlibiez, santoso.wijaya, vstinner
Date	2011-10-03.23:08:55
SpamBayes Score	0.03754185
Marked as misclassified	No
Message-id	<1317683336.46.0.903118608795.issue13081@psf.upfronthosting.co.za>
In-reply-to

Content
Without the aforementioned minidump library, you can also kick off the Python interpreter using a debugger (or have a debugger break into an already-running one) [1]. When the crash happens--presumably the debugger will break at this point--you can export the mini dump into a file for us to look at [2]. [1] I like using windbg (http://msdn.microsoft.com/en-us/windows/hardware/gg463009). [2] It would be something like, `.dump /ma C:\path\to\crash.DMP`

Without the aforementioned minidump library, you can also kick off the Python interpreter using a debugger (or have a debugger break into an already-running one) [1]. When the crash happens--presumably the debugger will break at this point--you can export the mini dump into a file for us to look at [2].

[1] I like using windbg (http://msdn.microsoft.com/en-us/windows/hardware/gg463009).

[2] It would be something like, `.dump /ma C:\path\to\crash.DMP`

History
Date	User	Action	Args
2011-10-03 23:08:56	santoso.wijaya	set	recipients: + santoso.wijaya, vstinner, brian.curtin, rlibiez, amorilia
2011-10-03 23:08:56	santoso.wijaya	set	messageid: <1317683336.46.0.903118608795.issue13081@psf.upfronthosting.co.za>
2011-10-03 23:08:55	santoso.wijaya	link	issue13081 messages
2011-10-03 23:08:55	santoso.wijaya	create