Very frequently, while I am trying to rebuild the solution IDE spit out the message 'Error: The operation could not be completed' in the output tab one or more times.
Simply open the file and press Ctrl+Shift+B to build and then Ctrl+F5 to run or use a right mouse button click and select Run to Cursor. While I am debugging the applications FORTRAN code/libraries, I occasionally stop the execution, change the source, recompile, and debug again. is broken off and you will not get an object file or an executable program. debug_line 0001e523 0000000000000000 0000000000000000 004885b5 2**0ģ6. Single Fortran files can be compiled and run without creating a project. Different compilers will produce different object codes from the same source. $ bazel build -s :mithral_wrapped -strip=neverīazel-bin/mithral_wrapped.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID=28bd192b145477c2a7d9b058f1e722a29e92a545, not strippedģ0. $ objdump -h bazel-bin/mithral_wrapped.so | grep debug #even with -s option, no '-s' was printed in gcc command
I had to add -strip=never to my bazel build command to get gdb to work, -compilation_mode=dbg may also work. In this case Linux did indeed need -g on the linker options.īazel can strip binaries by default without warning, if that's your build manager. I won't claim to fully understand why this helped, but I wanted to pass this on for others just in case it helps. I ultimately solved the problem by adding -g to the linker options. The curious thing was that 'file' reported debug not stripped on the target executable. Ultimately I tried gdb proper on the remote board and it complained of no symbols. My compile line options (Linaro gcc) included -ggdb -O0 as many have suggested but still the same problem. My issue was that the debug session would start and the program would execute, but breakpoints did not work and when manually paused "no source could be found" would result. Tool chain is Linaro 4.9 using gdbserver on the remote board and the Linaro GDB on the local PC.
SIMPLY FORTRAN THE DEBUGGER EXECUTABLE COULD NOT BE LOCATED PC
The setup is local PC running Debian 8 using Eclipse CDT Neon.2, remote ARM7 board (Olimex) running Debian 7. I know this was answered a long time ago, but I've recently spent hours trying to solve a similar problem.
0 kommentar(er)
