How to fix the error "No source file named ...\main. Eclipse when debugging with gdb [closed]. After a while, I seemed to find the cause and solution for this. It was because Eclipse seems to used a wrong path to main. GDB doesn't like this: I tried to fix this by adding a relative path that points to the absolute path instead. In Debug Configuration - > Source, I added Project - Path Relative to Source Folder that point to the project. And made sure it's above the Default path.(/attachment/d.
- 'No source file named ' problem while debugging. News: As usual while. >>>>>cb_gdb: > break 'C.
- Join the Stack Overflow community to: Ask programming questions Answer and help your peers Get recognized for your expertise.
- > 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.
- Subject: Re: No source file named. in gdb; From: Jim Ingham <email@hidden> Date: Tue. (gdb) break UStaticText.cpp :384 No source file named UStaticText.cpp. (gdb) pwd Working directory /Volumes/Development disk/MyApp.
- . and I can connect to the gdbserver on the device but I am unable to set breakpoints due to the following error from gdb: 496-break-insert. &'No source file named /home. GDB can't see debug info for that source in.
- Hi, I'm sorry but I don't know a suitable mailing list of this problem. Now I just feel like I'm into gdb, thanks to all of you. But I quite often face to a troublesome problem. When I set break point to file, gdb can't find.
After that Eclipse will set breakpoint using relative path and I was able to debug and set breakpoint, resume, etc.
I'm not able to set breakpoints anymore because gdb says No source file named D. No, I copied them to my local project source to. >>>>>cb_gdb: > break 'D.
. I got 'No source file named. ' in the gdb trace. \main.c' when adding a breakpoint in Eclipse when debugging with gdb. I ran into the problem when I can't set a break point when debugging with the GNU ARM J-Link.
Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search.