[news.eclipse.tools.cdt] Re: CDT GDB No source file named ... error

[Derek <subs@xxxxxxxxxxxxxxxxxxxxx>]

My guess is that you have the Source lookup path wrong for the debug 
configuration. Look in the Source tab of the debug configuration.

btw: it is recommended that when moving projects between machines, you 
should Export and then Import, rather than copying.

T Kruse wrote:
> Hi,
>
> I am using CDT on Eclipse 3.4.2 to develop on a large C project, which 
> has its own custom makefiles.
> I am facing problems with debugging, which I could not resolve after 
> spending hours on google looking for solutions.
>
> I had everything run perfect on Debian 32 for a while. I then copied the 
> workspace to a different PC, running Debian 64 bit, with different home 
> directory.
> I made a make clean and make, and I am able to run the application 
> without problems. However, when i try to set breakpoints, it does not 
> work. While the application runs with the c files I set the break points 
> in, if I add another breakpoint, I get in the gdb console:
>
> (gdb) 
> 300*stopped,reason="signal-received",signal-name="SIGINT",signal-meaning="Interrupt",thread-id="0",frame={addr="0x00007f13ba656c93",func="??",args=[],from="/lib/libc.so.6"} 
>
> No source file named gnuplot.c.
> (gdb) 301-break-insert gnuplot.c:103
> &"No source file named gnuplot.c.\n"
> 301^error,msg="No source file named gnuplot.c."
>
> The same happens for absolute paths. The debugger can stop on startup at 
> main, and the debugger works fine with a HelloWorld c app in the same 
> workspace.
>
> Would this be due to that SIGINT, and does anyone here understand what 
> causes this and how I may fix it?


--
Derek