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 THRlWiTi
Recipients THRlWiTi
Date 2015-06-15.15:57:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1434383850.99.0.136251358232.issue24455@psf.upfronthosting.co.za>
In-reply-to
Content
# Open a module using IDLE
# Run the module (Press F5)
# Activate the debugger ([DEBUG ON])
# Set a breakpoint in the module
# Run the module again
# Run the module for the third time
# Hit the Quit button in Debug Control window (twice, as the first click appears to do nothing)

Congratulations! You got yourself a crash!
After a while, a window dialogue appears asking "Do you want to end this process?". Click "End Process" (As there doesn't seem to be any other way).

One way to avoid this crash is to press quit before the third run. But even without it, this shouldn't happen. Sometimes the programmer may simply forget that there is an active debugger running...

I'm using 
Python 3.4.3 (v3.4.3:9b73f1c3e601, Feb 24 2015, 22:43:06) [MSC v.1600 32 bit (Intel)] on win32
(Windows 8.1)
History
Date User Action Args
2015-06-15 15:57:31THRlWiTisetrecipients: + THRlWiTi
2015-06-15 15:57:30THRlWiTisetmessageid: <1434383850.99.0.136251358232.issue24455@psf.upfronthosting.co.za>
2015-06-15 15:57:30THRlWiTilinkissue24455 messages
2015-06-15 15:57:30THRlWiTicreate