New submission from irdb:

# 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)

components: IDLE
messages: 245384
nosy: irdb
priority: normal
severity: normal
status: open
title: IDLE debugger causes crash if not quitted properly before next run
versions: Python 3.4

Python tracker <>
Python-bugs-list mailing list

Reply via email to