Eclipse Community Forums: C / C++ IDE (CDT) » Eclipse 2019-06 looks for glibc source code

Home » Language IDEs » C / C++ IDE (CDT) » Eclipse 2019-06 looks for glibc source code(Can't find a source file at "/build/glibc-LK5gWL/glibc-2.23/libio/ioputs.c")

Eclipse 2019-06 looks for glibc source code [message #1810507]

Mon, 12 August 2019 17:08

Eclipse User

When I press F5 to step into the next line, I get the following error:

Can't find a source file at "/build/glibc-LK5gWL/glibc-2.23/libio/ioputs.c"

It seems like Eclipse is looking for the source code for the glibc file.

Is this normal behaviour, and how can I fix this please?

TIA

Keith

Attachment: gdebugger-source-not-found-2.png
(Size: 23.21KB, Downloaded 135 times)

Re: Eclipse 2019-06 looks for glibc source code [message #1810643 is a reply to message #1810507]

Thu, 15 August 2019 01:32

Eclipse User

Don't step into it?

If you have the source, then you can set the path to it in
Run --> Debug Configurations ... -> <the applicable launcher> --> Source tab
Or use the handy Locate File ... button as shown in your image.

The debugger is searching for the source starting at the root directory named /build.

This will make setting the path much harder.
Maybe you could use a symlink for /build.
Assuming of course, you actually have the code.

[Updated on: Thu, 15 August 2019 01:35] by Moderator

[SOLVED] Re: Eclipse 2019-06 looks for glibc source code [message #1810654 is a reply to message #1810643]

Thu, 15 August 2019 05:24

Eclipse User

Thanks for your reply David.

Yes this is the correct behaviour.

I'm running Linux Mint Mate 18 Sarah 64 bit.

F5 steps into a function

F6 steps over a function

F7 steps out of a function

So if the debugger is on a libc function like printf() and I press F5 the debugger will attempt to step into the C source code for printf().

This is what you want if you are debugging the libc library.

I've not had this happen before so maybe the previous time the glibc library was not compiled with debugging info enabled.

I just need to remember to use F6 so I don't try to step into any libc functions.

Obviously if I did want to debug glibc functions, then I need to install the source code packages, and the error message should go then.

Kind Regards,

Keith

[Updated on: Thu, 15 August 2019 05:26] by Moderator

Previous Topic:	creating shared library from c source files generated from matlab
Next Topic:	printf and scanf behave poorly in Eclipse 3.5 on Windows

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 04 11:55:52 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter