I have been trying to establish connection between STM3220G-EVAL board and OpenOCD debugger under Eclipse Neon.2 (release 4.6.2) running on Windows 7 PC.
My Debug Configuration looks like: . The problem is that I still receive following Error Message: . I have found in another thread that this message is due to the missing line -f board\stm32f4discovery.cfg so I have appended it. But the result is still the same. Does anybody know what the reason could be? Thanks for any suggestions.
You've set this option in the GDB section, not OpenOCD section. Check "Start OpenOCD locally" and move the "-f board/stm32f4discovery.cfg" line to "Config options" instead.
Eclipse Neon.2 is broken for hardware debugging. Your only option is to downgrade to Neon.1.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=509812
Related
I wish to debug GNU Emacs in Eclipse IDE for C/C++ on my macOS Sierra. I have downloaded the source code with Git and built the project successfully via the command line. I then imported the project to Eclipse as an existing Makefile project with the GNU autotools toolchain setting.
I can now run the Emacs GUI from Eclipse. However, when I try to debug it (with gdb), I get the following error message:
'Launching emacs-26.0.50.1' has encountered a problem.
Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program terminated with signal ?, Unknown signal.
During startup program terminated with signal ?, Unknown signal.
I managed to get rid of this error by specifying the full path to the .gdbinit file in the Run > Debug Configurations... > C/C++ Application > emacs-26.0.50.1 > Debugger > GDB command file: textbox.
I now get a different error, but this is a matter for another question...
I had a similar error message while using the debugger for a small dummy code. I used the suggestion given in this link and got it fixed. In short, I had to change the debugger to an older one. Hope that helps if you are still having the same issue.
The problem for me was using USB 3.0 port. Connected board to USB 2 port and it was working fine.
I installed Eclipse luna with ARM plug-in, installed Segger software, attached a J-link base to my board. Running the command line Segger software it seems to connect just fine.
But in Eclipse, it's not seeing the J-link option and can't start the debugger. For some reason it's not showing up in the debug configuration options.
On a co-worker's machine it's working fine. We're comparing setups but so far haven't found any discrepancies. We both have Windows 7.
If I try to debug it pops up a window saying it encountered a problem:
Error with command: gdb --version
Cannot run program "gdb": Launching failed
Thanks for any help!
Okay, it appears that somewhere in my attempts to get this going, I had clicked on the box for the GDB SEGGER J-Link debugger in Window | Preferences | Run/Debug | Launching | Launch Configurations.
I thought that was a box to include that debug option, but it is a filter to exclude that debugger, and that is apparently why it didn't show up in the debug configuration window.
"Basheclipse installation issue" does not address my issue and thats why I ask a new question.
Hi, I am running Eclipse Luna on Windows 7
I followed all the instructions on http://sourceforge.net/projects/basheclipse/files/
I have never worked on Eclipse. I am stuck on 7th step(pasted below)
7) Switch to The Debug perspective. Start the debugging session. Launch "script.sh" from bash shell.
Please help me do this.
When I used the debug button it says "Launching new configuration has encountered an error Bash is already running."
I tried the run button and it says "Couldnt find Interpreters. Do you want to configure interpreters now?"
edit:ok the debug perspective is on now.
edit:ok looks like a bug
http://sourceforge.net/p/shelled/discussion/399718/thread/6272268c/
any way to circumvent this?
"Launching new configuration has encountered an error Bash is already running."
--> just relaunch your eclipse and then it will work without any problem.
"Anyone tried installing Eclipse and debugging on a Linux machine?"
--> yes. eclipse neon and jdk 8.
You can follow my tutorial at http://dietrichschroff.blogspot.de/2017/07/bash-enabling-eclipse-for-bash_14.html
I could not debug using goclipse plugin, it was asking about gdb debugger then I downloaded the binary ver. 7.6 but now it is giving me "Source Not found"..
As suggest from many posts, I tried to build the program before going to start debugging but still it is giving me the same thing.
below is a secreenshot
even I found some guys were saying is to specify the working directory in configuration as "other" but still giving me the same error
finally, I fixed the issue by using the "gdb" distributed within liteide package. you could reference it from "Window | Preferences"
I'm trying to add Aptana to my Eclipse installation. I'm trying to do so on Win7 x64. I've tried both x86 and x64 versions of Eclipse. Most of the time Eclipse would install just fine, run okay, but as soon as I try to pluin Aptana it has problems. It will start up, then encounter an error immediately and close. Right now I have the x64 version installed fine. When I start it up it throws the error but doesn't close. I can close the error window and continue using Aptana just fine. I've attached a couple screenshots to show what the error is and what my current Installation Details look like. Let me know if there's any other information I could provide.
Thanks in advance.
Aaron-
Open the 'Error log' view, you probably see the stack of the NPE.
Then try to google the solution.