I am using latest version of Eclipse ie Kepler in that how to update/install the "GDB OpenOCD Debugging" plug-in tool.
You can download the plugin here: http://gnuarmeclipse.livius.net/blog/plugins-install/
Just paste http://gnuarmeclipse.sourceforge.net/updates link into the "Work with:" field of the "Install new software" window of Eclipse (available from the Help main menu).
There are several components and GNU ARM OpenOCD Debugging Support is one of them.
But latest versions of OpenOCD work very well with the regular GDB Hardware Debugging.
Related
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
I'm trying to analyse (valgrind) a program on linux using QtCreator. But the menu in qt creator is disabled.
I have OpenSuse 13.1. linux on 64bit. This is what i tried so far:
I've checked the plugins dialogue and the Valgrind plugin is greyed out, but selected.
I've checked the installation directory and the plugin is there.
Valgrind is installed (valgrind --version -> valgrind-3.8.1)
valgrind works (valgrind --tool=callgrind ./myprog)
I tried the stock version of QtCreator (2.8.1) and a newer installation in ~/bin/Qt.. (3.4.0)
I tried it with a qmake and a cmake project.
I tried to re-enable the QtQuick plugins. This made the menu work and the Analyse icon on the left appeared, but still no valgrind support.
Can anybody help?
You might need to enable the Devices->RemoteLinux plugin as well.
I'm using eclipse with CDT on mac osx mavericks. I've installed gdb using macports. But I'm not able to set custom debugger in preference set.
When I go to preferrnce->c++->Debug->? there is no debug option where I can set custom debugger. Online eclipse CDT documentation suggest debug menu in this preference set. I've tried Kepler as well as Luna but still issue persist.
I'm not sure what's wrong with my eclipse. Please help. Thanks
http://i.stack.imgur.com/RYD9A.png
Open "Debug Configurations" from the debugging icon, then choose Debugger tab and specify the gdb command path "e.g. /usr/local/bin/gdb"
After that you have to give gdb permission to control other processes, follow steps mentioned in the reply of this question:
debugging in eclipse using gdb on mac - Failed to execute MI command: -exec-run
Is it possible to use Qt Creator (MinGW build) as just-in-time debugder? Instead of VS on windows.
Every time, when my application crush, Windows propose me to use Visual Studio as debugger.
From QtCreator : Launching the Debugger article:
The post-mortem mode is available only on Windows, if you have
installed the debugging tools for Windows.
The Qt Creator installation program asks you whether you want to
register Qt Creator as a post-mortem debugger. To change the setting,
select Tools > Options > Debugger > Common > Use Qt Creator for
post-mortem debugging.
You will need to set it up as per documentation:
GDB On Linux and Windows, use the Python-enabled GDB versions that are installed when you install Qt Creator and Qt SDK. On Mac OS X, use the GDB provided with Xcode. You can also build your own Python-enabled GDB. Follow the instructions in Building GDB.
Here you can find the wiki for building GDB yourself:
Building GDB
I am attaching a screenshot from my QtCreator on Linux where you can configure your debugger related options if it is not recognized by default.
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