|
| Re: Eclipse 2019-06 looks for glibc source code [message #1810643 is a reply to message #1810507] |
Thu, 15 August 2019 05:32   |
David Vavra
Messages: 1426
Registered: October 2012 |
Senior Member |
|
|
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 05:35] Report message to a moderator |
|
|
| [SOLVED] Re: Eclipse 2019-06 looks for glibc source code [message #1810654 is a reply to message #1810643] |
Thu, 15 August 2019 09:24 |
 Missing Name Missing Name
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
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 09:26] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03053 seconds
] 
Search
Help
Register
Login
Home
