Debugging in SlickEdit

[Clark]

If Project>Close Workspace is enabled, you have a workspace open that can be closed. Maybe I misunderstood your post "I did this and the Build menu options seem to be the ones referring to a Python project, not a single-file one."

[gkl]

There is no such option though, it is greyed out (as in attached image).

[Clark]

That means the Build menu items should be for a single file project. What Build menu items do you see when a python file is active?

I see:
Execute
Python Options
Add New Build Tool...

Execute works for me. Does it work for you?


I can also use Debug>Step Into or set a break point and use Debug>Start

[gkl]

This is the thing; the first image is from a SQL Server single-file project and I get the expected options under Debug. The second image is from the Python file, the options for a single-file Python project are no longer there. When I select Step Into, I get the error message in the third image.

[Clark]

"This is the thing; the first image is from a SQL Server single-file project and I get the expected options under Debug"  Incorrect statement. The internal debugger for single file project is started from Debug>Start or Debug>Step Into.

I don't know why Debug>Step Into doesn't work for you.

Has SlickEdit's Python debugging ever worked for you on this machine?

If so, when did it stop working?

[gkl]

Apologies, that should read I am getting the correct single-file options under Build, not Debug. I am getting the option about the port shut down from the beginning when I tried Python debugging. What else can I try to make sure the port is not in use or how can I research what might be blocking it - is there some kind of enhanced debugging in SlickEdit, so that if I enable verbose debugging and send you the logs, you would be able to make some sense out of it?

Best Regards,
George

[Clark]

Go to Macro>Set Macro Variable and set "def_debug_logging" to 1.

I think this will just end up showing us that the socket communication isn't working. No work around I know of for that.

Logs are written to <configdir>/logs/debug.log and dapcom.log