bluebird75 / winpdb

Fork of the official winpdb with improvements
Other
91 stars 24 forks source link

error message on windwos #40

Open Ben8565 opened 3 years ago

Ben8565 commented 3 years ago

When i run winpdg on windows i have this message 👍

La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.

Current directory: c:\Users\Benoit\projets\tproj

Command to be executed: "C:\WINDOWS\system32\cmd.exe" /C """C:\Python37\python.exe" "session_manager..\rpdb2.py" --debugee --pwd="i3ELQQAm" --rid=9823679 "c:\users\benoit\projets\tproj\tdebug.py" ""

ConEmuC: Root process was alive less than 10 sec, ExitCode=1. Press Enter or Esc to close console... I think the tools does find the file session_manager..\rpdb2.py. I work on Windows 10 Python 3.7 and the last version of winpdb winpdb_reborn-2.0.0.1 Successfully installed Winpdb-reborn-2.0.0.1 numpy-1.19.4 pillow-8.0.1 wxpython-4.1.0

bluebird75 commented 3 years ago

Can you show me the exact command that you ran to get this result ?

bluebird75 commented 3 years ago

I see the problem and I just fixed it. Can you try with the latest git version ?

Ben8565 commented 3 years ago

I try the new version: I have a similar message : La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.

Current directory: c:\Users\Benoit\projets\tproj

Command to be executed: "C:\WINDOWS\system32\cmd.exe" /C """C:\Python37\python.exe" "C:\Python37\lib\site-packages\winpdb_reborn-2.0.0.1-py3.7.egg\rpdb..\rpdb2.py" --debugee --pwd="nB4hq4Yg" --rid=4437256 "c:\users\benoit\projets\tproj\tdebug.py" ""

ConEmuC: Root process was alive less than 10 sec, ExitCode=1. Press Enter or Esc to close console...

My command is λ python -m winpdb .\Tdebug.py
19:28:47.100 rpdb2.py:6138 MainThread/92452 setrecursionlimit(): rl = 1000
19:28:51.315 winpdb.py:3006 MainThread/92452 set_font(): Using font "Courier New" for Console
19:28:51.320 winpdb.py:3006 MainThread/92452 set_font(): Using font "Courier New" for Console
19:28:51.719 session_manager.py:1291 Thread-2/84872 _spawnserver(): Terminal open string: 'start "rpdb2 - Version RPDB 1_5_0 - Debuggee Console" cmd.exe /K ""C:\Python37\python.exe" "C:\Python37\lib\site-packages\winpdb_reborn-2.0.0. 1-py3.7.egg\rpdb\..\rpdb2.py" --debugee --pwd="nB4hq4Yg" --rid=4437256 "c:\users\benoit\projets\tproj\tdebug.py" "'
19:28:53.250 session_manager.py:1103 Thread-2/84872
wait_for_debuggee(): Scanning for debuggee...
19:28:56.260 session_manager.py:1103 Thread-2/84872 __wait_for_debuggee(): Scanning for debuggee...
19:28:59.280 session_manager.py:1103 Thread-2/84872 __wait_for_debuggee(): Scanning for debuggee...

bluebird75 commented 3 years ago

It seems that winpdb does not handle well the fact that is was installed as an egg.

The execution command tries to locate rpdb2.py to launch the debugee. However, this fails in egg because rpdb2.py is not accessible as a single file.

Until I find a proper solution, you can solve this by installing winpdb either directly from git or without resorting on an egg. If you have a full winpdb directory in site-packages, this should work better.

pjfarleyiii commented 3 years ago

Just adding my experience with winpdb. When I start my program with winpdb with this command:

python -m winpdb myprogram.py

The winpdb GUI is displayed, but in the debugee window I get this:

C:\Users\MyUserID\.virtualenvs\envtest-4VBVv3XT\Scripts\python.exe: can't open file 'session_manager\..\rpdb2.py': [Errno 2] No such file or directory

Environment: Windows 10-64 V2004, Python 3.8.5, using pipenv shell for a virtual environment.

pip list output:

Package        Version
-------------- -------
numpy          1.19.5
Pillow         8.1.0
pip            20.3.3
PySimpleGUI    4.33.0
setuptools     49.6.0
six            1.15.0
wheel          0.35.1
windows-curses 2.2.0
winpdb-reborn  2.0.0.1
wxPython       4.1.1

When you said to install winpdb "directly from git" do you mean use git clone to clone winpdb into the (virtual in my case) the Lib/Site-packages directory? After uninstalling winpdb with pip first, correct?

TIA for any clarification you can provide.

Peter

[Edit]: Same error and behavior occurs in a non-virtual command shell environment.