From: Andreas Schwab <schwab@suse.de>
To: "Jirka Koutný" <koutnji2@gmail.com>
Cc: gdb@gnu.org
Subject: Re: question about why gdb needs executable's binary
Date: Wed, 13 Mar 2019 14:34:00 -0000 [thread overview]
Message-ID: <mvm7ed2sv18.fsf@suse.de> (raw)
In-Reply-To: <CAH5nFm8dpqyFWuttO+aZOCBAAMjEeuEtv=xwhyFjjMpu8cTs3g@mail.gmail.com> ("Jirka =?utf-8?Q?Koutn=C3=BD=22's?= message of "Wed, 13 Mar 2019 14:24:50 +0000")
On Mär 13 2019, Jirka Koutný <koutnji2@gmail.com> wrote:
> 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?
A core file only contains data from modified mappings. Any data from
read-only mappings needs to be read from the original files.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-03-13 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 14:25 Jirka Koutný
2019-03-13 14:34 ` Andreas Schwab [this message]
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=mvm7ed2sv18.fsf@suse.de \
--to=schwab@suse.de \
--cc=gdb@gnu.org \
--cc=koutnji2@gmail.com \
/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