I use Ubuntu 18.4.4 and GCC 7.5 and i downloaded eclipse installer and installed 2020.3. CDT for c++
now when i try to debug the code using step over.it works fine in main function going line by line but when it gets into called function ,step over just jumps to next break point as if it is resume.
i am new to eclipse and I do not know what is the wrong??
i found some questions with same behavior for java.
is this the same problem but with C++??
this is another question with similar content without solution Debugging in Eclipse. Moving between breakpoints
Related
When I add a breakpoint, Eclipse freezes for some about 5 seconds. Sometimes it takes much longer until I can continue work, up to one minute. It does not depend on how I set the breakpoint (double-clicking on line numer, or via shortcut ctrl + shift + b) or which view is open (Java View, Debug View...) or if Debugging is active.
Removing a breakpoint works immediately without any problem.
The problem also only occurs in one workspace. I can't see any entry in the Error Log.
I'm using Neon.3 Release (4.6.3)
What could cause this effect?
This appears to be due to a bad index file. I deleted *.index in
{WORKSPACE}/.metadata/.plugins/org.eclipse.jdt.core and this fixes the problem. Note that by doing this, you're forcing Eclipse to re-index all .java files. Thus, the first time you go to add an Exception breakpoint, you can expect a wait of several minutes while all classes.
But once all things are settled for the first time, it will become smother.
I upgraded to Oxygen.1a Release (4.7.1a), but still had the issue. Then I deleted my workspace and set it up newly. The issue dissapeared. My assumption is that there were some corrupted configurations. However, it is solved with a new workspace (that worked for the older Neon version, too).
I am working in Linux Ubuntu 16.04 using OpenJDK 1.8 and eclipse v4.15 by installing java-2020-03. Eclipse froze occasionally during debugging but not always. To get around the freezing, I passed the VM argument -Dsun.awt.disablegrab=true. Now I can debug without freezing.
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.
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/)
Before this stupid program will explode my head to the 26th time...
I have
Win 7
Eclipse Luna 4.4.0 Build 20140612-0600
Photran 8.2.1
Cygwin Devel Packages gfortran + make (used)
MinGW with g95 (installed but not used because no make.exe)
So I downloaded the Hello World example, changed it a bit
program HelloW
implicit none
integer i
i=1
print *,i
print *, "Hello MPI World"
i=i+1
print *,i
i=1000
print *,i
end program
1) So problem (or most probably a mega-feature) number one.
The default debuggers (Run->Debug Configuration->Debugger) gdbserver and minGW gbd don't work, because they need .gdbinit. I created an empty file .gdbinit, but it doesn't help. I could find no info of what must be inside.
OK, no wonder that just another Eclipse feature doesn't work. Next one:
2) As debugger I chose gdb/mi. It seems to work without .gdbinit.
I set a break point in front of integer i line.
I start the debugger but it looks like it runs till the end of the program and suspends there (the last line end program is lighted green).
Now if I press F5 it starts to move in the program step by step from the very beginning, but it needs 3 button presses to do 1 line. It first jumps forward, nothing happens, then it jumps back, and on the 3rd press it jumps forward again and execute the line (e.g. the variable i changes).
What the hell is that?
I used Fortran Compaq and Intel Visual Studio without any problems. Now I f**ck with these "free" programs for 2 weeks now, and nothing works properly. Starting from the outdated help in eclipse, to dead g95 compiler.
I'm runnung Eclipse (indigo) 3.7.1 with Xdebug 2.1.3 on Ubuntu 10.04 LTS, PHP 5.3.2-1ubuntu4.14.
My problem: While debugging Drupal installation everything works fine, adding breakpoints, stepping in, over, return, vars are showing as they suppose to. But, once the execution flow takes me to the other file which holds the definition of a function being called in the first file, I get an error message saying: "Unexpected termination of script. Debugging ended.".
Show super global vars is switched off in Xdebugger options (solution I found previously), and 'Path Mapper' is left blank in PHP server options (another solution).