slicerrt / slicerdebuggingtools Goto Github PK

Following the instructions of the tutorial http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly/Extensions/DebuggingTools. The application crashes without showing a folder dialog after clicking the selector.

I have reproduced this error with two different compiled versions of Slicer.

Update: The application does not crash if the path of pycharm-debug.egg is manually typed. After that everything works correctly.

absence .so file."pydevd-pycharm.egg/pydevd_attach_to_process/attach_linux_amd64.so to exist." why?,but there have the attach_linux_amd64.so,waht can i do to solve this problem.

When trying to connect PyCharm (version 2020.3.5) to Slicer (version 4.11.0-2020-09-22) I am constantly getting an error saying

Expected: /PyCharm 2019.3.3\debug-eggs\pydevd-pycharm.egg\pydevd_attach_to_process\attach_amd64.dll to exist.

but I am not sure how to fix this.

Currently the template for launch.json comes up with something similar to

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Remote Attach",
            "type": "python",
            "request": "attach",
            "connect": {
                "host": "localhost",
                "port": 5678
            },
            "pathMappings": [
                {
                    "localRoot": "${workspaceFolder}",
                    "remoteRoot": "."
                }
            ],
            "justMyCode": true
        }
    ]
}

But with a development setup (i.e. slicer built from source) the pathMappings parameter here might the debugger from stepping into slicer python code, this might also be a problem how i set up the workspace though, but removing the pathMappings entry allowed stepping into the base slicer python

I have been using Eclipse to debug my Python code with PyDev v7.0.3
When I updated the PyDev module to version 7.3.0 through the Eclipse IDE, Slicer was no longer able to connect. The following error message appeared in the Python Interactor

Traceback (most recent call last):
File "C:/Users/cjohnson/AppData/Roaming/NA-MIC/Extensions-28438/DebuggingTools/lib/Slicer-4.11/qt-scripted-modules/PyDevRemoteDebug.py", line 158, in setup
if self.logic.isConnected():
File "C:/Users/cjohnson/AppData/Roaming/NA-MIC/Extensions-28438/DebuggingTools/lib/Slicer-4.11/qt-scripted-modules/PyDevRemoteDebug.py", line 575, in isConnected
return pydevd.connected
AttributeError: module 'pydevd' has no attribute 'connected'

Comparing the pydevd.py scripts for both versions shows that in 7.3.0 there is no longer a global variable 'connected'.
This error leaves the Slicer Debugger module in a strange state - not allowing me to change the location of the pydevd.py file back to the older version. I had to manually change this in the Slicer.ini file.

I am using Slicer version 4.11.0-2019-08-13

Using the Windows nightly that had qt5 (from 01/19).
When checking the "Auto-connect on next application startup" checkbox, an error is sometimes thrown, as seen below:

This seems to stem from what is returned from QSettings.value() when the value set is a boolean. From what I can tell from my bit of testing, this happens regardless of if the value is either True or False, sometimes returning u'true' or u'false' or the boolean equivalents. When boolean is returned is when the error occurs, due to the lack of a .lower().

I've had trouble testing further as it seems it happens when the settings get written to and read from a file rather than just setting a value and reading it from QSettings().

Slicer just crashes when the remote debuggers port is wrong

I have a professional PyCharm, and I followed the wiki tutorials but in my debug-eggs folder i only see pydevd-pycharm.egg. I don't see any pycharm-debug.egg

PyCharm 2019.1.3 (Professional Edition)
Build #PY-191.7479.30, built on May 29, 2019
JRE: 11.0.2+9-b159.60 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-54-generic

on Slicer 4.11.0-2019-07-19 r28397

Ubuntu 16.04 LTS

Any comment is appreciated

I would be nice to provide the possibility to let the user change the port number of the remote debugger to connect to

When I try to connect to PyCharm from the latest nightly version of Slicer, I get the following error message when I click "Connect to debug server":

Note that this error does not occur with older versions (e.g. Slicer 2017-06-26), where I can successfully connect.

OS: Windows 10
Slicer: Slicer 2017-07-20 (latest nightly)
PyCharm: 2017.1

Slicer log file attached.
Slicer_26159_20170721_103713.txt

The current information is valid for older versions of Visual Studio 2017. On an up to date VS2017, I needed to use the legacy debugger. Debugging was possible - good. But as older versions of Visual Studio go out of support, it would be good to add information/support for newer versions (e.g. VS2022).

When the button is clicked, the window pops up as if everything is normal, then it disappears
When the window pops up, and there is an error it is reported in the Python console in red.
However, I am afraid when users don't have the Python console shown, they have no idea what is going on.