Using GCC/GDB from within Eclipse - stopped working?

[Richard von Lehe]

Has anyone had the problem recently of trying to make or debug from within GCC and hitting an exception immediately? I believe I picked up an update to Eclipse because after closing Eclipse and reopening, I hit this error on projects that have been rock-solid. If I find anything out, I'll posts, but I'm wondering if this has happened to others recently. I've probably had Eclipse open for 2-3 weeks, so that's the time frame. Note: the exception is not in Eclipse itself, but I believe it's use of an external GNU tool or tools? Grr.

[Richard von Lehe]

Here's an example of output from an attempted build. You can see that the makefile starts to be processed, evidenced by the debug output. It seems to choke when it tries to compile the first source file:

13:36:22 **** Build of configuration Default for project pacpow_p5 **** make -f Makefile.barebones.mak debug OUTPUT_PATH = BARE build-directories is BARE_build hex is BARE_build\BARE_s110.100.1.hex hexconfig is BARE_build\BARE_s110.cfg.hex targets is BARE_build\BARE_s110.100.1.hex BARE_build\BARE_s110.100.1.sum.hex BARE_build\BARE_s110.100.1.all.hex BARE_build\BARE_s110.100.1.icast.hex BARE_build...icast.hex BARE_build\BARE_s110.100.1.bin BARE_build/BARE_s110.out ICAST_BUFFER = 0x2F000
make: Interrupt/Exception caught (code = 0xc00000fd, addr = 0x4227d3)

13:36:22 Build Finished (took 223ms)

[Richard von Lehe]

I should note that the project compiles fine at the command line using the same makefiles.

[Ole Morten]

I've seen this as well, but for me it is dependent on which shell I run make from. From Windows' cmd.exe, it works fine, but from Git Bash, it fails. According to this Super User question, this may have something to do with the PATH environment variable, so it could be worth trying to change that in some way.

[Richard von Lehe]

I had seen the comments about PATH and parentheses. I actually reinstalled the GNU tools to NOT be in the (x86) path, and am still trying to move GnuWin32 out of there as well. That's where I get my 'make' from. In the mean time, I don't have this problem with GDB after I specified the full path to the executable in the debug configuration.

[Ole Morten]

Good to hear that you got it working! I'll definitely keep the full-path trick in mind in case of future such problems. Feel free to post your solution as an answer separately, and accept it if you think that solved your question! :)