I recently moved from Java to C++, and experiment using Eclipse CDT. I created a HelloWorld project, which compiled and run fine.
I then tried to enable the debugger, but couldn't get it running properly. Below is my debugger configuration (I am using gdb in Mac Sierra, gdb installed using homebrew, codesigned already). Please advice what additional setting I might need to do in order to get debugger work. Thank you!
Related
I'm trying to debug my st device(STM32F401CCU6) remotely. I'm using raspberry pi 3 for debugger. I had install openocd on RPI. I set everything up in STM32CUBEIDE 1.8.0.
When I debug my code appears this message box. I search a while. I did configure "stm32f4xx.cfg" file for device ID.
RPI3 ready to debug
STM32CUBEIDE 1.8.0
I did solve with downgrade from STM32CUBEIDE v1.8.0 to v1.6.0. I can flash program and debug. But there is one more issue. I want to use live expressions when debugging. But it doesn't work like this.
I just switch to try develop on Linux for a while.
But one thing I couldn't understand how to solve it, as I mentioned in topic.
I'm going to develop a project that need Java SDK, then I installed the SDK with command:
#bash
sudo apt install openjdk-17-jdk-headless
After installation finished, I could run command java -version and javac -version to see the result of installation and it looks OK.
openjdk version "17.0.3" 2022-04-19
OpenJDK Runtime Environment (build 17.0.3+7-Ubuntu-0ubuntu0.22.04.1)
OpenJDK 64-Bit Server VM (build 17.0.3+7-Ubuntu-0ubuntu0.22.04.1, mixed mode, sharing)
And then when I open IDE (Intellij IDEA) and it has feature of integrated terminal. (see picture)
But when I try to test java -version it was shown the error:
bash: java: command not found
As you can see from picture, I run java -version on terminal it return output properly, but when I run the same command java -version, it output with error message, like it couldn't find the java SDK that I installed.
Could anyone help me to describe the reason and solutions to solve the issue?
P.S. This is same on VS Codium.
I found the answer.
Solution:
Install the IDE app with the file from official website instead of using package manager of OS.
Description:
The cause is I installed the IDE via Package Manager of OS (here I'm using Pop_OS, install via Pop!_Shop)
And its package manager has some strict rules for security purpose.
I'm not sure, Pop_OS using which package manager, but I'll raise Flatpak as reference: https://docs.flatpak.org/en/latest/sandbox-permissions.html
And on blacklisted directories, my installed java command is under /usr/bin/ which is in blacklist.
I used all commands as in omnetpp installation guide (https://doc.omnetpp.org/omnetpp/InstallGuide.pdf) and also according to this answer. The $ make command worked and I also verified installation with:
$ cd samples/aloha
$ ./aloha
which started using qtenv.
but the problem is that the $ omnetpp command doest work with after printing
Starting the OMNeT++ IDE...
and eclipse IDE does not open.
is it possible to use this IDE in m1 Macs?
is there any alternate IDEs to workaround?
You did not specify what version of OMNeT++ you were trying to run. I'm assuming 5.6.
OMNeT++ 5.6 relies on the system-wide installed JRE to run the IDE. That may NOT be present on your system if you are running on ARM. OMNeT++ 6 and 5.7 comes with a built-in private JRE, so the IDE should work with those versions also in intel emulation mode.
I upgraded golang from v1.11 to v1.13 in mac (mojave OS). The debugger started throwing error Test framework quit unexpectedly. The console output was
API server listening at: 127.0.0.1:xxxxx
Version of Delve is too old for this version of Go (maximum supported version 1.12, suppress this error with --check-go-version=false)
Debugger finished with exit code 1
I am unable to use debugger on goland since then, however delve as cli command is working. Dont know how to proceed? Also I cannot find any option to disable --check-go-version in goland?
Update your IDE to GoLand 2019.2.2 or newer and the issue will be solved.
I get the pop up "Failed to start terminal for debugger".i have set the gdb path in the gdb options of codelite. Is there anything else to be done?
My mac os version is 10.10.4
GDB version installed under /usr/local/bin/gdb - version 7.8.1
The c project created a simple hello world to test the codelite usage on mac os and unfortunately not able to launch gdb.The compilation is going through fine
On OSX, the recommended the debugger is LLDB.
Please use it instead.
Project settings->general->Debugger, and select "LLDB Debugger"
EDIT, Sep 06:
I have uploaded a new OSX build (8.2.3) with this problem fixed.
http://codelite.org/support.php