linux - What is the recommended way to perform source-level debugging of system library calls? -


I need to debug some calls in the system library, to understand how the call is different, and why a Or the other will fail.

Compromised system libraries and separate debug symbol files for Linux Distros, for example, /lib/libc-2.8. Therefore, symbols have been stripped, leaving information behind a section called .gnu_debuglink that contains information to find a different debug file. Separate debug files are installed through the debug package, and contain the symbolic information required by GDB. It is well described and

After installing the debug package and sources, I was hoping that GDB symbols and sources would be available and I would be able to see the listing and take steps in the calls. Instead, GDB tells me "no line number to go for xyz"

I've verified that the debug-file-location is correct, and the directory is set to source directories.

Is it possible to do what I want to do? Am I going to go wrong about this? Is there an easier way?

Did you have the debug-file-directory parameter in GDB? According to the documents that you have provided, you should do what you want:

Set the set debug-file-directory directory which GDB provides separate debugging notification files You can set up multiple directory components in a directory by searching for a directory separator.

show debug-file-directory Show GDB searches for separate debugging information files in directories.

For example in my Fedora distribution, the directory is / usr / lib / debug .

You can also define it by compiling it over time Configure - Together-debug-dir = / usr / lib / debug ...

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -