I'm trying to debug my project using the "step-into" function, but each of the debug options (other than Debug Project, Attach Debugger, and Debug Core File) is grayed out. I've checked on both my Linux and Windows machines, and they both have the same problem.
I'm running Netbeans 7.4 with gdb 7.6, seemingly properly loaded under tools->options->C++. Is there possibly a compatibility issue with newer versions of gdb? If so, how can I revert to an older version?
Thanks!
Here are some things you can try:
Remove all breakpoints of your project and try again with a new one
(If possible) test version:
a earlier version of GDB
and newer version of NetBeans (current stable: NB 7.4 SP2 -- testing: NB 8.0 RC1)
Are there any error messages? Please also keep an eye on NetBeans's logfile - on IDE start and debugging
Check your paths, e.g, to compiled binaries / libs
Maybe this Bug can help you: Bug 233683 - Gdb doesn't work with NetBeans 7.3.1
It's posted for 7.3, but maybe it's still in 7.4.
Related
I've macOS Catalina and Eclipse IDE for C/C++ Developer, Version: 2021-03 (4.19.0) and I need to use EclipseCDT debugger. Following the steps at macOS 10.15 Catalina gdb problem for C++ Debugging in Eclipse I still have problems. Namely, the Debug window doesn't show up.
The only difference between my steps and the ones from the tutorial is the gdb version: mine is 10.1, while the other is 8.3.
I've found this FAQ link: https://wiki.eclipse.org/CDT/User/FAQ, where seems to be possible to use LLDB debugger, but I can't find the detailed instructions. Any approach is fine to me, I just need a working debugger
I have a problem in debugging OMNeT++ in my Macbook Pro.
I installed OMNeT++ 5.6.2 on my MBP having macOS Catalina 10.15.5 and tried to run tictoc tutorial. It runs fine, however there is a problem with debugging.
I know that masOS no longer supports gdb and we have to install gdb through Homebrew or Macports and then configure it. I already have set up gdb.
In order to test gdb, I installed eclipse CDT, set up and configure GDB, then started debugging.
It was debugging fine in eclipse. However, when I debug in OMNeT++, it stucks at "Configuring GDB".
I also tried with OMNeT++ 5.5.1 but having the same problem.
I also asked it before at stack overflow, but couldn't find appropriate solution.
MyPreviousQuestion
Does anyone know how to fix OMNeT++ debugging issue on macOS?
Just like in the other SO question: I would also advise to try to use OMNeT++ 6.0 preview 8 on macOS. I have successfully built it on macOS 10.15 and as suggested in the other SO thread, it does use lldb instead of gdb.
An alternate workaround could be to use VS Code with an appropriate extension. I have just published a blog entry related to debugging OMNeT++ models:
https://omnetpp.org/blog/2020/07/05/omnetpp-debugging-tips.html
When I try to debug my c++ program in Eclipse (Neon 4.6.2 on mac), the progress bar stops at 33% and the operation eventually times out. I get an error saying:
Error in services launch sequence -
Command '-list-features' is timed out
I've verified my GDB build and uninstalled and reinstalled using brew multiple times. GDB works perfectly in terminal, but I'm not able to run it in eclipse at all and I greatly prefer having a GUI when debugging. I have ensured that the path to the debugger in the eclipse debug configuration is correct. In addition, I've tried adding -g as a debugging flag.
Any help/suggestions would be great!
This sounds like a known problem with CDT 9.2, See Bug 509737. It is fixed for 9.2.1 released in a month or so. Your choices are to downgrade CDT to 9.1 or to install the most recent, but unreleased, build of 9.2.1.
I use Netbeans 8.0 on Ubuntu 14.04 and I have run into a problem with debugging c++ files. In the past this has worked. According to what I see on Google, if I go to the project properties I should see
General
Build....
Run
Debug
Related Projects
In my case there is no debug entry, which explains why I can't debug. I went to the repository and removed and reinstalled gdb. Then I removed Netbeans and reinstalled it as well. In case there was something wrong with my project, I made a new c++ project and it too was missing the debug capability.
Anybody have any idea what else I can do? This has to be something fairly basic but I can't guess what else I can do.
Thanks,
Ilan
I got a similar results with NetBeans 8.02 on Ubuntu 12.04.
Some projects are unable to be run with debugger. Some can be debugged.
The same project, complied on Ubuntu 12.04 but with NetBeans 8.0 (without updates) runs with debugger with no problems.
So it seems to be a version issue of NetBeans.
I got a new Macbook Air and installed XCode 5 on it. To my surprise Apple does no longer ship gdb with the command line tools. As I am doing lots of c++ coding I am dependent on a good debugger.
What I tried so far:
Install gdb 7.6 via macports and signed the binary.
Debugging from QT-Creator is possible. It stops at the breakpoints but I see no information at all about the stack. Using lldb not possible, I get a weird python error.
Debugging from Netbeans is not possible at all. The Debugger is not stopping at any breakpoint. Apart from that Netbeans is not working with lldb.
Working with XCode is no problem. Everything works as expected.
Problem is I need an IDE that can do remote debugging as I have several Raspberry Pi projects. Developing software directly on the pi with vim is fun but not suitable for bigger projects.
So the question is, has anyone a working debugger on Mountain Lion with XCode 5 installed? IDE in question needs to support remote debugging (eg QT-Creator, Netbeans, Eclipse)
Thank you!
Install Xcode 4.6.3. If you have a developer's account it's available for download at http://developer.apple.com
Encountered the same problem. Finally installed command line tools from xcode 4.6.1 on ML. This package is available on Apple site. It installed GCC-LLVM 4.2.1 and GDB 6.5. Qt Creator was able to build application and start debugging. Debugging is not stable too much; but i can to see call stacks, values and stop on breakpoints. I use it for 32bits build - maybe it matters.
You could also switch from GDB to using the LLDB debugger (although the Qt support is early for this).
See http://stanford.edu/~rawatson/lair/mac.html