| Cant find source file [message #1140327] |
Wed, 16 October 2013 05:26  |
Eclipse User |
|
|
|
Hi,
I am an eclipse(CDT) and Ubuntu(13.04) user. I recently ran a C project. When I run it, there is a seg fault at some line, when I try to debug it using a debugger, I get the below error.
Can't find a source file at "/build/buildd/eglibc-2.17/malloc/malloc.c"
Locate the file or edit the source lookup path to include its location.
I have not used eclipse debugger for C program in Ubuntu before.. It would be great if someone could help me on how to resolve this issue.
Regards,
Mani
|
|
|
|
|
| Re: Cant find source file [message #1717377 is a reply to message #1717112] |
Sat, 12 December 2015 06:51  |
| Eclipse User |
|
|
|
Don't know about auto continuing but for inadvertently stepping into a library routine you can use the finish command to run until the current routine finishes, that is, returns. The eclipse debugger view shows this as a bent up-arrow.
In this case the program stopped within a library routine with a segment fault. You don't want to continue running.
Instead you should walk back through the stack trace if you want to see how the program got there.
I find this far more informative. An "only-show-my-code" switch is just laziness IMO. When stepping through the code you should simply step over things not yours. When the program halts unexpectedly, I personally want to exactly where. Even it I don't want to know, it's quite easy to find where things went wrong in my own code.
Every option comes with a cost: code bloat, extra testing requirements, and yet another way things can go wrong. Eclipse is a fine example of what you get when you try to accommodate everybody: a gazillion options that sometimes result in bizarre interactions. Just read the posts here to see how many steps, and how much understanding, is needed because of all the options.
|
|
|
Powered by
FUDForum. Page generated in 0.03626 seconds
Home