Multiple stacks when trying to debug python

[rowbearto]

When I tried to debug my python program, which runs under 'execute', I got multiple stacks.

You can find it on support at stack_pydebug.log

[patrick]

The top part of the first exception is cut off, but I suspect it's a problem we've been working on with the debug view getting garbled after back to back debug sessions. Once that happens, your next debug session will usually fail to start.

You may need to remove your vrestore.slk to work around this.  Before you do that, could you upload it to the same directory as the stack? 

[rowbearto]

Look for pydebugstack.tgz on support.

I put the vrestore.slk there as well as an updated stack log that shouldn't have the beginning cut off.

I will try later debugging with a deleted vrestore.slk.

[rowbearto]

If it helps I do notice that when it switches to debug mode that all my tool windows are gone and I have just 1 giant editor window.

I will try later to debug again after removing vrestore.slk.

[rowbearto]

I deleted (actually renamed) the vrestore.slk. When I try to debug again I get more stacks.

I have uploaded a new tarball to support:

pydebugstack2.tgz

This new tarball has the new stack.log after removing vrestore.slk as well as the new vrestore.slk file after closing SE.

[rowbearto]

I'm not using any hotfix on 25.0.1. Should I be?

[patrick]

Oh.  Yes there is a fix in hotfix 1 for stacks starting up the debugger in mainwindow.e

[patrick]

Actually, hold up, that's not in hotfix 1, it's staged for hotfix 2.  If you apply hotfix 1, I believe I can send you a file to load with the fix in a few minutes.

[rowbearto]

OK, while you wrote that last post I tried again with hotfix1 and still got stack.

I uploaded stack.log, vrestore.slk (after deleting before the debug session), user.cfg.xml and about .txt into a tarball on support:

pydebugstack3.tgz

[patrick]

Here's the file that is fixed for the next hotfix.  "load" that from the SlickEdit command line, restart the editor, and then start the debugger.

The changes match up with your stacks, so I think this is all it is. 

[rowbearto]

OK, no stacks now after your fix. But now I have just 1 big editor window. When I debug I usually also have many tool windows like the call stack, breakpoints, Open, Files, Search, etc. If I add them manually will they be there again next time I debug?

If I restore my old vrestore.slk is there a chance that it wouldn't crash and I get all those tool windows back?

[rowbearto]

Looks like if I add tool windows in my debug session that they will return in my next debug session.

[rowbearto]

I added the "Output" tool window to my debug session but then the debug session shut down. Now everytime I try to start a debug session it shuts down. I see a "Warning" tab in the bottom right: 'Debugger stopped, socket shut down".

[rowbearto]

Nevermind, it is because I removed my breakpoint that it is shutting down. It actually runs to completion.

[patrick]

Ok.  Your original vrestore.slk may not be better, if it was overwritten after the stack that interrupted the initial restore.