A few days ago, Eclipse for C/C++ (Helios) stopped running my programs. They can be compiled with MinGW without displaying any errors. However, when the programs are run, Eclipse always get stuck at "Launching Delegate" at 70%. No matter how long I wait, the program never starts. The same happens when I try to run the program from the command line; no matter how simple the program, the command line just does nothing, as if it is waiting for the program to start.
I believed that this was just an issue with my Eclipse workspace, so I created a new workspace and tested a Hello World application, but it failed too. I reverted to an older version of Eclipse (Indigo), and a 32-bit version, but these had the same error. I even installed a different IDE, Netbeans, but it too never runs any programs. So, clearly, it's not just Eclipse. I tried reinstalling MinGW, but this also didn't help.
I have tried everything I can possibly think of. I could only find one other person with the same problem online, and theirs was never answered. Can anyone help me out with this strange issue?
I had the same problem. Always stuck at 70%. However, it turned out that somehow it can be fixed by disabling my anti-virus program, when I want to run a C/C++ program. Which I find to be quite strange.
I hope it helps.
Related
After upgrading to Python 3.6, Eclipse debug mode stopped working properly. It renders an error like this:
The strangest thing is that this issue does not raise in 100% of cases. Sometimes it goes away. And then again arises. I am lost trying to figure out why.
Although it happens when you're running the PyDev debugger, the debugger is probably only exercising some path in your code which has a bug and is usually not exercised (and thus leads to such an error).
In this case, attach a c/c++ debugger to the program to find the culprit (you can use the attach to after that error is hit)... On Windows you can use Visual C++ and on Linux GDB.
-- as a note, the issue is probably on some c/c++ library you're using (but given the info, it's really hard to pinpoint anything).
I'm following these instructions to remotely debug a python script http://pydev.org/manual_adv_remote_debugger.html
Using breakpoints and stepping work without a problem, but after resuming the script (without any other further breakpoints) the script executes the remaining instructions, and then hangs instead of exiting normally. Even closing the server from pydev does not help, I have to Ctrl+Break the script
I am sure I've done this a while ago with an older eclipse+pydev, and the script resumed and exited normally (and it's very important for me not to mess the rest of the execution).
I've tried this with both Eclipse Luna and Liclipse pydev_4.0.0.201504132356, pydev_4.0.0.201504092214 on Windows 7 x64, same behaviour
Is this an intended behavior or a bug? How could I make pydev let the script end normally?
I can't reproduce this here... please report that as a bug adding details on how to reproduce it (i.e.: ideally, create a project on github and add a step-by-step on how to reproduce it so that it can be fixed... without being able to reproduce it properly, it may be pretty hard to fix).
Also, please give details on the OS and Python version used in the report (https://sw-brainwy.rhcloud.com/tracker/PyDev/)
I have a strange problem when using Pydev on my work machine (others at work have the same issue). It does not occur when I do this at home, which makes me think it's something to do with the environment at work. We are running Windows 7.
I am using Pydev 3.9.2 but the same thing happens with earlier versions. It occurs with all versions of Eclipse after 3.7. The problem is this. When I create a jython console (the one running in the Eclipse VM), the error output doesn't work. If I type an invalid python command, there is no output on the console. It just appears that the command worked. If I type a command such as "print 100", the output prints as you would expect.
The second problem is that if I hit the red square which is supposed to remove the console window, Eclipse crashes. There are no errors or any indication of what is going wrong.
I have tried different versons of eclipse, different versions of Pydev, different machines and it doesnt make any difference.
Has anyone seen this? I've tried everything I can think of to debug this issue so any help is appreciated.
thanks,
brian
Unfortunately those quirks are expected...
The internal console in Eclipse is mostly a developers SDK for experimenting with Eclipse itself and is not meant as a general shell (you should configure an interpreter and use it for that).
I don't have plans on improving on that situation (there's already a multi-year backlog on PyDev and this isn't really critical), but if you'd be willing to spend some time and fix those issues, pull requests would be definitely welcome -- see: http://pydev.org/manual.html for details on getting the code and setting up the environment.
Installed Eclipse-Kepler on a Windows 8 box. Clojure and Leiningen already installed. Installed Counterclockwise. Started up, created test Clojure project, ran without debugger, and ran successfully under debugger. Messed with it a bit more, was in and out of the debugger several times. After one debugging session got "an error" (yes, I know I should have written it down, but failed to do so. Take pity upon the soul of this poor sinner...). After that every debugging session I tried to start (using "Debug As...Clojure Application") failed to start, eventually timing out with a "Timed out waiting for REPL to start" error. Messed with it a while, uninstalled CCW, re-installed CCW - no change, REPL still refused to start under the debugger. Could always start a REPL by "sending" the text of the project file to the REPL using Ctrl-Alt-S. Finally deleted all of Kepler, re-installed, re-installed CCW, and could then debug again.
My questions: has anyone else encountered this, and is there a better workaround than blowing away the entire Eclipse install and re-extracting from the .zip? I did do a check for updated versions of anything and nothing came up. Is this a Kepler issue, i.e. might this be more stable under Juno?
I'm trying to debug a sample QT project in eclipse in Ubuntu. Launching debugger hangs at 93% for several minutes. Then every step of debugging is very slow.
I tried to debug a simple hello-world-program. Debugger flies. So, the problem is with QT.
Looks like gdb traces terminal prints a very very long PATH, can't see the beginning, ends with this:
...:/usr/src/linux-headers-3.0.0-13-generic-pae/lib/lzo:/usr/src/linux-headers-3.0.0-13-generic-pae/lib/raid6:/usr/src/linux-headers-3.0.0-13-generic-pae/lib/raid6/test:/usr/src/linux-headers-3.0.0-13-generic-pae/lib/reed_solomon:/usr/src/linux-headers-3.0.0-13-generic-pae/lib/xz:/usr/src/linux-headers-3.0.0-13-generic-pae/lib/zlib_inflate:/usr/src/linux-headers-3.0.0-13-generic-pae/lib/zlib_deflate:$cdir:$cwd
What can the problem be?
Apparently, the debugger is trying to load a lot of symbols for the said program (including Qt) and this may take quite a while (so, it's not Qt-specific.)