I have looked as thoroughly as I can, and I have found no solution to my issue. I'm on RHEL 8 using the C/C++ Eclipse IDE v2021-3 and while my IDE once stopped at breakpoints, it no longer does so. So my experience is that it simply runs through to completion as if a normal Run was performed, regardless of where I place my breakpoints.
Things I have tried that have not worked:
Ensuring that Skip All Breakpoints is disabled
Cleaning and rebuilding the project
Ensuring that my breakpoints are attached to code that is being executed
Ensuring that Eclipse is up to date.
Restarting Eclipse
Crying
Updating gdb
Things I have not tried:
Redownloading Eclipse, since it isn't installed on my machine, and it's freshly updated, I didn't do this
Any thoughts? Thank you in advance!
Related
Downloaded & Installed/unzipped Eclipse 2020-9 to see if my old version ( Mars ) was broken.
When I do something simple like
Add a Folder
I get two "create folder dialogues"
2 popups
Same when I right click to delete a folder, I get two delete dialogue boxes.
these are just two examples, I'm guessing most actions will have two reactions!
Cannot debug a target get an error ( Stop the first session before staring a new one )
guessing Run->Debug is fired twice too.
I'm a long time eclipse user, so really curious why this is happening
issue started when I got a 'new' win 7 pc, discovering this bug while setting up my environment
any hints are welcome.
Used OpenJDK and Oracles Java 8 same issue ( Tried two versions of eclipse, same issue )
Eclipse is used for C development with ARM MCUs with OpenOCD and Gcc for ARM.
Many thanks for taking time to read this.
Regards
Alan
Solution:
Fixed nVidia graphic driver application software was the culprit, the one that makes enhances the user experience by making windows go transparent when you drag them, good useful stuff like that. Uninstall nVidia desktop enhancing tools and Eclipse (and Notepad++ ) work perfectly Eclipse was never the problem, just the side effect.
I'm working with simple c/c++ console projects in Visual Studio 2017.
After a build, if I run/debug it from within the IDE (Ctrl+F5 or F5), there's always a strange wait of tens of seconds before it actually runs (e.g. if I printf on the first line of my main(), it won't show until after the long "wait")
If there's no build after this first run, and I Ctrl+F5 or F5 again, it runs fast and normal. If then I change some source code and rebuild it, the strange wait appears again.
This slows down the dev iterations so much, and definitely feels wrong. Just wonder if any guru here can point me to a solution/workaround?
Thanks in advanceļ¼
OK, mystery resolved -- it's my Avira antivirus. Somehow after installing VS2017, it starts to scan each new exe I generated. After setting my dev folders as exceptions, things are a lot quicker. Finally.
The cygwin bash console only resets the cursor to the top of the screen, it does not clear the screen. vi does funny things with the cursor - hard to explain, but the cursor seems double wide when in vi. top output is mostly double-spaced, but sometimes single spaces.
When I use mintty I have none of these issues.
I've tried all kinds of settings in the last several hours, too many to list. Seems like I'm going backwards. I've got conemu working great on another computer, and I've tried replicating the setup but there must be something I'm missing.
What information can I provide to help solve these issues?
I've someone else runs into this issue: you probably need to set TERM=cygwin in your .bashrc.
Turns out the problem machine had an old version of Cygwin. Mintty received a major upgrade in July 2015. Numerous other packages have been upgraded also in the 2 years since I installed Cygwin in that machine. After upgrading Cygwin, the problems went away.
I just discovered this problem today, and I had no idea what caused this problem. My project had been developed for few months.
I have a project(solution), with several projects in there, it works well if I write and debug, by pressing F5.
The problem occur is when I press Ctrl+F5 (to skip debug mode), or run directly from double click the exe, it crashed. The errors dialogs that pop up every times are different, but OutOfMemoryException is the most frequent one.
I had checked to make sure all my projects are .Net 3.5
I put a MessageBox.Show("something") at the beginning of my main project constructor, but it never reach.
I use some registry cleaner to clean/fix my registry, scan for viruses.
I had try to read the meaning of each error and exception, but still no clue why it happen.
These are a series of screenshots if I press Ctrl + F5. (FutureGenerator is some random name I gave to my project.)
Series of screenshot if I run the app from my debug folder, FutureGenerator.exe
I suspect this is caused by framework crashed during Windows Update, but I removed those update that I performed recently, still same. The exe file works on other non development PC, but I don't want to reformat my PC or reinstall my VS, yet, because it's a painful process.
Any idea, anyone?? Million thanks.
You mention v3.5 but the very first screenshot is about v4.
Try repairing your Framework 4 and/or VS2010
I found the problem. It's actually because I added FutureGenerator.exe into Application Verifier by Microsoft. The verifier only support debugging testing.
After I removed FutureGenerator.exe from the Application Verifier, everything's ok.
debugging in MonoDevelop does not work for me. First of all, I have installed MonoDevelop, GNU Debugger plugin and ctags through Ubuntu software center and I'm using Ubuntu 10.10.
When I press "Debug" it goes into debug mode but very quickly returns to "normal mode". My simple application contains some scanf so it should wait for input and I have also set a lot of breakpoints.
My application works perfectly when I run it without debugging and it debugs fine if I use gdb manually. Of cause, I've tried rebooting and installing multiple times.
Any ideas on what goes wrong?
Update:
I have checked the MonoDevelop log and it goes like:
OnTargetEvent, type - TargetExited
...
Thanks, Lasse
I suggest you file a bug.
You might want to check for errors in the MD log (~/.config/MonoDevelop/log) and the debugger output pad. Also, are you using an external console?
It have now been fixed :) : https://bugzilla.novell.com/show_bug.cgi?id=624776