Recently I asked a question and one of the guys here really tore into me about not using a debugger. Someone else was nice and suggested Visual Studio C++. I have been trying to work with it and it was really nice until I tried more complex code.
So I decided to try eclipse since that is the IDE I prefer. I got through the missing .gde file problem.
Now the debugger opens but It is only debugging assembly code files. This does me no good if it is not stepping through my own code.
It does not even get to my breakpoints or my code.
It don't help me to step through code I didn't write.
I really hope someone can help with this.
So the question is simple :
How to get Eclipse CDT to Debug my code I write and to stop and recognize breakpoints???
Below pic is what I am getting.
I finally just went with Visual studio, not my choice but it work better than the others for a debugger.
Related
I downloaded an Eclipse's extinction for Rust, but then, after creating a new Rust project, i got this problem
I tried to follow some instuctions that I was able to found, including some from this website. I deleted and then downloaded Rust on my computer, I deleted and downloaded Eclipse, same with VS C++ building tools, but all this didn't help. I saw, that for some people helps to just reenter current workspace, but it was not my case. Despite this problem, default code seems to run OK, but it is almost impossible to edit. If someone had this problem or just know how to solve it, can you help please?
P.S. My English probably is not very good, so sorry for mistakes.
This is a known issue. Update to the latest proper TM4E release from https://download.eclipse.org/tm4e/releases/latest/ so that you have the bundle version with this class present.
As I was coding in Visual Studio code, I wondered if someone had created a tool for auto-completing the console log code.
Sure enough, someone had written a workflow for it, and I'd have to say it's pretty phenomenal.
Since the author explains it so thoroughly and well, here's the link to it.
I really don't know how to explain my problem. My IDE just stopped 'helping' me coding. As an example in the picture below when I used to write 'this.' the IDE should suggest me all my properties/methods. right now as you see nothing happens no matter how long I'm waiting. looks like something messed up over there, I tried to install it again but same result.
Forgot to update: after installing it again and update it -problem solved.
So basically I want to drive myself crazy while disciplining myself learning to program. I want to kick it old school and really understand what I'm doing. I don't want Eclipse to hold my hand and tell me that I have a syntax error or that I have any errors except for when I run my code and the console tells me something is wrong. I have searched and searched and searched online and I cannot find where you disable anything. I've been to the editor/compiler preferences and changed everything to ignore instead of warning, but eclipse is still holding my hand.
I'm using Eclipse Luna for Java. Any suggestions or help at all would be greatly appreciated!!!
The closest I think you'll get is to disable the automatic, incremental compilation (menu Project > Build Automatically). But that doesn't disable the Java editor's natural tendency to highlight obvious syntactical errors as you type.
To be honest, if you really want to avoid all of the guidance that an IDE like Eclipse gives you, you'd probably be better off using a "plain" text editor (possibly with simple syntax coloring), such as TextPad or Notepad++, along with command-line javac. But I don't think that will actually help you learn better; it certainly doesn't help with the exploratory/discovery part of learning.
Im using Eclipse Luna.
I want to edit some code in the middle while i debug the code. That is, I connected to a server and try to debug code,So at some point i want to edit the code make it to run.
Is that possible in Eclipse? I think this can be done in IDEA..Not sure how can i do that in eclipse?
You can definitely edit the code while debugging, although that would not have any effects on the currently debugged process. You have to relaunch the debug process to see the effects.