public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27713] debug symbols are present, but still getting "No symbol table info available."
Date: Tue, 13 Apr 2021 01:16:38 +0000 [thread overview]
Message-ID: <bug-27713-4717-bHLEHCcz9M@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27713-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27713
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to winnie from comment #2)
> Hi Andreas,
> Thank you for your reply. So what can I do in order to check if "it is
> detailed enough, or that every part of the object is covered." Since I'm
> struggling with this for a while now, I am happy to provide any information
> in order to understand what's going on.
What I would normally do is use "readelf -wi" (or equivalent formulation
for objdump) and pipe through a pager, then search for the particular
compilation unit I'm interested in.
Like, does "MXNDArraySyncCopyToCPU" appear?
One typical failure mode is to have some particular file compiled
without debuginfo, maybe it was missed by "make clean" or something like that.
gdb could be a bit more helpful in diagnosing this situation.
Though of course, without debuginfo it can't supply source file
names, so maybe the best it could do is some kind of generic warning.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-13 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 15:49 [Bug gdb/27713] New: " nagyt at nexus dot hu
2021-04-09 16:34 ` [Bug gdb/27713] " schwab@linux-m68k.org
2021-04-09 17:13 ` nagyt at nexus dot hu
2021-04-13 1:16 ` tromey at sourceware dot org [this message]
2021-04-14 9:50 ` nagyt at nexus dot hu
2021-04-14 13:00 ` tromey at sourceware dot org
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=bug-27713-4717-bHLEHCcz9M@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).