I have community edition version 5.0.2 of PyCharm. My Python version is 2.7.
The problem is simple.
In the 'Run' mode everything works fine. But when I try to insert breakpoints and launch 'debugging' mode, it does not stop at breakpoints. However, corresponding debugging window is appearing and buttons to "resume", "stop" and "pause" are there. But if I try to "stop" or "pause" it does not take any effect. Program works like it is in 'run' mode.
C:\Python27\python.exe "C:\Program Files (x86)\JetBrains\PyCharm Community Edition 5.0.2\helpers\pydev\pydevd.py" --multiproc --qt-support --client 127.0.0.1 --port 56284 --file C:/Users/.../.../main.py
pydev debugger: process 8112 is connecting
Connected to pydev debugger (build 143.1184)
None
([], 75)
Process finished with exit code 0
What could it be? In other Intellij products (such as Intellij Idea) I did not encounter such a strange issue.
Could anybody help?
Related
I recently shifted to mac M1 from ubuntu and I have installed VS code and tried to debug the project but it didn't stop at any breakpoint.
You must start the sever before the debugger will go to the break-point. Once you press run wait until it is finished
https://code.visualstudio.com/docs/python/tutorial-django
Summary: debugger ignores breakpoints on Appceleration Titanium Studio IDE.
I'm using Appcelerator Studio, build: 4.10.0.201709271713, fresh install on macOS 10.14.1 (Mojave). My iOS project compiles and runs on the simulator just fine, everything behaves properly normally.
When I try and debug, however, execution ignores any breakpoints and just barrels on. I've checked all obvious settings, tried setting breakpoints every way possible, no luck.
If I launch the app under debug in the simulator and just let it sit there, eventually a dialog box will pop up saying "'iOS debugger on simulator...' has encountered a problem. Debugger failed to connect".
Anyone out there know what to do from here? I've been using Studio for years and the debugger part has always 'just worked'. I'm not sure where to look for port and connection settings.
I have an ncurses program that I'd like to interactively debug using CLion. The problem is that when I run the program in CLion to debug it, the inbuilt console where the program is run doesn't display the output of the ncurses program properly.
I'd like to have the program run in my systems terminal so I can see the output properly whilst debugging the program with CLions debugger.
Is there any way to do this?
The best way to accomplish this is to use GDB now it can be really frustrating to get started so Ill show you how I accomplished it in linux
open a terminal and go to your project debug file and type gdbserver localhost:1234 ./myFile
open clion to myFile project and in the upper right corner you should see a build all (or your projects name) click it and go to "edit configurations"
in the upper left corner you should see a plus sign, click it and press "GDB remote debug"
then in "target remote" type tcp:127.0.0.1:1234
Next in "path mappings" press the plus and type /location/to/file/myFile (same file as in 1.) in both Remote and Location
Press OK and in the upper right corner select the name of the configuration that you just made and press debug
you might need to try to restart the gdbserver one more time for this to work but if you did all the steps above you should see a debug prompt come up and on the terminal you should see your project running.
There are some limitations with this for example you always have to run gdbserver localhost:1234 ./myFile command on your terminal for it to work.
Some Video/documentation that helped me:
Debugging with GDB at 33:35 (Video by JetBrain)
GDB documentation on Jetbrain
I hope this helped :)
In other debuggers, you would do this by running the ncurses application in a terminal, and attaching the debugger to the process using ncurses.
Doing that avoids interference between ncurses (which changes the terminal I/O modes) and the debugger's command-line.
The attach feature is a recently released feature of the CLions debugger:
Further reading:
More power to debug: Attach to local process (January 20, 2016)
CLion 1.2 roadmap (August 31, 2015)
Debugging in CLion (May 8, 2015 )
CLion answers frequently asked questions (September 16, 2014)
Debugging ncurses application with gdb
Using GNU's GDB Debugger:
Debugging Ncurses Programs
I am trying to run the pycharm debugger but he not working, for all my files (which he work for them last night)
this is the erorr:
C:\Python27\python.exe "C:\Program Files (x86)\JetBrains\PyCharm Community Edition 5.0.1\helpers\pydev\pydevd.py" --multiproc --qt-support --client 127.0.0.1 --port 60124 --file C:/Users/User/PycharmProjects/untitled/test.py
pydev debugger: process 6168 is connecting
Connected to pydev debugger (build 143.595)
Process finished with exit code 0
I was stuck on the same issue for a while, but reading over these two threads at the developer's site made me find the issue:
Pycharm debugger not working
Debugger not working: code is executed normally
In my case, it was because the Breakpoints setting had become incorrect somehow. To fix it, go to the Breakpoints menu by clicking here (or CTRL+SHIFT+F8):
Then set the settings to something like this. The top option Enabled was disabled in my case.
After this, it worked as usual in my case.
--
Versions:
Pycharm 2017.1.1 professional
Python 3.5.1
Django 1.10
Remove all set breakpoints and then retry debugging. To do this press <CTRL>+<SHIFT>+<F8> then select all breakpoints then click the (-) button. This problem can occur across multiple versions.
I am using Komodo IDE 7 with a Django 1.4 using Python27.
I have been using the remote debugging option of Komodo IDE 7 but it seems to not responed to my breakpoints. If I break in my model decleration/setting.py it does break for the first time but it seems to "disconnect" after the first initialization.
the command I am running the debugger is :
set KOMODO_PATH="%ProgramFiles%\ActiveState Komodo IDE 7\lib\support\dbgp\bin"
c:\python27\python %KOMODO_PATH%\pydbgp.py -d localhost:9000 manage.py runserver --noreload
Figured out that this is a bug in Komodo 7.02. It seems that Django 1.4 uses a multi-threading machanisim which doesnt work well with Komodo.
A bug was filed but for a while there is a work around : using --nothreading while starting manage.py.
However, it seems to effect performance badly !