From: "Ananthakrishna Sowda (asowda)" <asowda@cisco.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: GDB cannot figure out shared libraries from core, but proc map shows the list
Date: Thu, 9 Jun 2022 22:11:56 +0000 [thread overview]
Message-ID: <SJ0PR11MB5917270A24DAB25F98BC7EF1CFA79@SJ0PR11MB5917.namprd11.prod.outlook.com> (raw)
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?
reply other threads:[~2022-06-09 22:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR11MB5917270A24DAB25F98BC7EF1CFA79@SJ0PR11MB5917.namprd11.prod.outlook.com \
--to=asowda@cisco.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).