Problem with lldb-mi and Eclipse on MacOs - eclipse

I installed lldb-mi following the documentation. At the moment I have the executable in the directory "/usr/local/bin/lldb-mi", and when I launch it I get the following output.
I configured Eclipse for C++ to choose lldb-mi for the debugging. I have no errors, but debugging doesn't start. It just seems to build, how could I fix this?
Update: I launched the application from the terminal and when I start debugging it tells me: Unable to find full path for "/usr/local/bin/lldb". In fact lldb is located in the folder "/usr/bin/lldb. Is it possible to move the executable?
I copied the executable, but the dubugger still does not work....
Thanks in advance for the answers.

Related

debugging rust on Eclipse Corrosion no longer works on fresh install

I change my Hard drive and so I made a fresh Eclipse Corrosion install but I kept my Rust projets. Problem is I get an error when I launch my prog in debug mode. It seems to work in run mode but I didn't test this that much.
Error is
An internal error occurred during: "Launching my_prog".
Cannot read the array length because "launchConfigEnv" is null
Important note : it seems to be link with the use of an input file (debug configuration/common/input file)
I try many things, many installs, new projects, many, many things but nothing works (and I cannot figure out what launchConfigEnv is).
Any help welcome...
Edit : I install 2019.12 Eclipse and it works fine. I will work a little with this version and try out more configuration to shrink the problem.
As a workaround, add a single environment variable to the launch configuration, as follows:
Once that is done, re-launch it and it should work.
Note that in order to get rust debugging working in Eclipse I installed MSYS2 and the following MSYS2 packages.
pacman -S mingw-w64-x86_64-gcc
pacman -S mingw-w64-x86_64-gdb
pacman -S man
I followed some instructions in the Rust Corrosion Trouble Shooting guide to get a working GDB.
Reference: https://github.com/eclipse/corrosion/blob/master/documentation/Troubleshooting.md#debugging-on-windows
The Rust debugger command needs to be changed to rust-dbg.cmd, as follows:
However, the PATH environment wasn't working for me, so in the rust-gdb.cmd script I added this near the top:
SET PATH=%PATH%;F:\msys64\mingw64\bin;F:\Data\.cargo\bin
(Adjust as-per your installation of MSYS2 and Cargo/Rustup)
After which Eclipse was able to start a debug session and stop at a breakpoint.

GDB Eclipse not finding Source Files

Recently I had a bug with my CDT eclipse application, so I downloaded GDB for debugging. It has brought me a lot of frustration. Finally, I have managed to properly install GDB, however when I try debugging my application, I get this error: No source file named /Desktop/workspace/TopVM/src/ShadowStack.h., as you can see there is an unnecessary . at the end of the path and it causes eclipse to freeze, so I have to force quit it. How would I go about fixing this?
as you can see there is an unnecessary . at the end of the path and it causes eclipse to freeze
This is not an unnecessary ., it is simply a full stop in the error message. It comes from GDB, probably this line:
throw_error (NOT_FOUND_ERROR, _("No source file named %s."), filename);
To fix the problem it would help if you identified if the problem is GDB or CDT, to do this, you can try running GDB without CDT and see if it freezes.
I assume you have found the following resources on setting up GDB on Mac (as I am guessing you are using?):
http://ntraft.com/installing-gdb-on-os-x-mavericks/

How do I run a .py module in Aptana?

Every time I try to run a .py module it just opens in Firefox.
I'm running Aptana in OS X 10.6
If you installed and configured PyDev, it should work.
Make sure you use the correct "Run" command. Prefer "Run as Python module", avoid "Run on Server".
If that doesn't help, edit your question and give an exact example what you do (which menus/buttons you click, etc).
See: http://pydev.org/manual_101_run.html for details on running a Python module (make sure you read the whole getting started: http://pydev.org/manual_101_root.html which should help you in getting your environment setup and gives some tips to properly use PyDev).
I used a same workspace for both python and java , and met the same problem.
If I change a new workspace, the Run As works. So i think there is something wrong with workspace settings.

"Launch Failed. Binary Not Found." Eclipse C/C++ IDE issue. [Eclipse installed on Windows 7 working with Cygwin]

I have two problems :
One ] I don't know how to use Cygwin and not sure if I have installed it correctly and
Two] My Eclipse displaying error every time Im trying to run any cpp program.
Actually I have downloaded Cygwin for Netbeans IDE which also not working. Cpp programs giving errors and nothing is executing.
Can u please tell me how should I fix these and can u give me some links to tutorial sites ,ideas ,- anything on how to use these.
I do not know if this will help you. But I found an answer that may be useful.
Launch Failed Binary not found Eclipse for C in Windows

Launch terminal from eclipse

I recently switched to Eclipse (Helios) for my programming needs, and I like it very much.
There is just on thing that is driving me crazy, how can I launch (compile and run) my code into the native mac osx terminal.
I tried creating an "external tools configuration", but that just starts the terminal without outputting the application.
What I do now is right-click on the binary in the Project Explorer and then "Open With" and then "Other" and then I pick the terminal app from the list. But this solution is driving me nuts.
Please help.
It's all about defining the External Tool correctly.
For example, the following should work if your selected file is a Unix executable.
Open a new External Tool configuration.
Set the location to /usr/bin/open
Set Working directory as ${selected_resource_loc}
Set the arguments to -a /Applications/Utilities/Terminal.app ${selected_resource_loc}
When you run make sure you select "src"
This should work. You could improve it further. You could even write an AppleScript that would do that and run it using osascript.