GDB cannot figure out shared libraries from core, but proc map shows the list

Ananthakrishna Sowda (asowda) asowda@cisco.com
Thu Jun 9 22:11:56 GMT 2022


I don’t understand the combination of these two outcomes I see in same GDB session on a non-native core-file.
(gdb) info shared
No shared libraries loaded at this time.

(gdb)info proc map
This command prints a complete list of shared libraries loaded with name and address-map.

GDB could not figure out link map information as seen by ‘No shared libraries loaded at this time’ message,  but it is able to print process mapping information.
Does it make sense to use the method used in “info proc map” as fallback if link map information cannot be processed by GDB?



More information about the Gdb mailing list