From: "Jirka Koutný" <koutnji2@gmail.com>
To: gdb@gnu.org
Subject: question about why gdb needs executable's binary
Date: Wed, 13 Mar 2019 14:25:00 -0000 [thread overview]
Message-ID: <CAH5nFm8dpqyFWuttO+aZOCBAAMjEeuEtv=xwhyFjjMpu8cTs3g@mail.gmail.com> (raw)
Hello,
If we assume debugging a core file generated by an excutable with stripped
symbols (that gdb is able to find and load correctly in my case),
I was wondering why does gdb still need the executable's binary as well? Is
there some additional information retrieved from the executable? It does
seem the stack trace does not get resolved if the executable file is not
specified, but if I understand it right, PT_NOTE contains address ranges
and shared libraries names as well, so the information to build the strack
trace is there already. So say if I only start gdb and then core-file
<corefilename>, why does 'where' return a list of question marks?
What is the missing bit of information there?
I'm not questioning correctness or anything, if it's like that from
historical reasons I'm cool with that, I'm just trying to understand the
thing.
Thank you,
Jirka
next reply other threads:[~2019-03-13 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 14:25 Jirka Koutný [this message]
2019-03-13 14:34 ` Andreas Schwab
2019-03-13 15:41 ` Jirka Koutný
2019-03-13 16:22 ` John Baldwin
2019-03-14 21:51 ` Jan Kratochvil
2019-03-19 14:25 ` Jirka Koutný
2019-03-19 14:35 ` Jan Kratochvil
2019-03-19 15:25 ` Jirka Koutný
2019-03-19 15:42 ` Jan Kratochvil
2019-03-19 15:47 ` Jirka Koutný
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='CAH5nFm8dpqyFWuttO+aZOCBAAMjEeuEtv=xwhyFjjMpu8cTs3g@mail.gmail.com' \
--to=koutnji2@gmail.com \
--cc=gdb@gnu.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).