Python debugging

[jporkkahtc]

Python debugging is causing me trouble.

Several times I've had the debugger abruptly stop for no apparent reason - as if I had done Project->StopDebugging.

Most recently while stepping, I hit F9 to set a breakpoint, and debugging stopped.

[Lee]

Does this appear to be a new issue or has this also been an issue prior to v23 Beta?  Anything you can reproduce with regularity?

[jporkkahtc]

Seems to be new, though python debugging has never been super reliable.

Its happening often today with the script I'm working on, I've not tried anything else.

[Lee]

Next time you are debugging Python, enable def_debug_logging and if it happens again send debug.log from config\logs.  See if we can figure this out.

[jporkkahtc]

Uploaded to jporkka-python-debug

At the end of the log there are lots of:
debug[2018-08-13T13:57:24Z]debug_gui_update_all: suspended=1
While the debugger it stopped at a breakpoint it seems to continue inserting these events.

I'd bet it is this noise that is interfering with expanding variables in locals or <add> in watches.

[Lee]

Are any of the Python modules using threading?  Trying to replicate it and trying to narrow down possibilities.

[jporkkahtc]

Probably -- just trying to debug some script that isn't quite working on my machine.
I'm debugging a simpler script right now, and it is not having this problem.

[jporkkahtc]

Maybe I spoke too soon.
Debugging a pretty simple single-threaded script and <add> in watches doesn't work.

The following:

Code: [Select]

debug[2018-08-14T12:44:46Z]debug_gui_update_all: suspended=1

is continually added to debug.log, at least while the script is suspended - about 10x per second.

[Clark]

Beta2 will be ready soon but won't address this issue. We will need more time to address this issue.