From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Regenerating debug files for debugging a core dump
Date: Wed, 26 May 2021 22:41:30 +0200 [thread overview]
Message-ID: <20210526204130.GI28754@pengutronix.de> (raw)
In-Reply-To: <20210526203203.oek2owdhx2y3xp56@pengutronix.de>
On Wed, May 26, 2021 at 10:32:03PM +0200, Roland Hieber wrote:
> On Wed, May 26, 2021 at 11:31:56AM +0200, Michael Olbrich wrote:
> > Hi,
> >
> > On Tue, May 25, 2021 at 04:43:54PM +0200, Guillermo Rodriguez Garcia wrote:
> > > I am trying to debug a core dump from a system based on ptxdist-2018.05.0.
> > >
> > > I see that the debug symbols are generated in
> > > platform-xxx/root/usr/lib/debug.
> > >
> > > The thing is that I don't have the original debug files anymore.
> > > If I regenerate the root fs and everything else from the same sources
> > > (ptxdist clean + ptxdist go), will the generated debug files be valid for
> > > debugging the core dump?
> >
> > It may or may not work. PTXdist tries to make builds reproducible. But
> > there are cases where it does not work and the resulting binaries are
> > different.
> > So it's worth a try if you don't have the debug files any more, but it's
> > better to keep them to avoid relying on this.
>
> Hmm, if the package does not build reproducibly, its build ID will
> change, so gdb won't find the debug symbols automatically. But does that
> also mean that the debug symbols cannot be loaded into gdb manually? If
No, gdb gets the build ID from the newly built binary, not the core dump.
So it finds the debug data, but if that does not match the original binary
it may not help.
> the BSP was built from exactly the same sources (even without
> reproducibility) most other data layouts, file names and line numbers
> should still be the same, right?
It depends on what's different. A small change often means that the rest of
the code is shifted a bit and then the addresses won't match any more.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-05-26 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABDcavZWsuJ8tRfr7iWMRuqZfnCFHAhwbaftf182UsCd7Yao5g@mail.gmail.com>
2021-05-26 9:31 ` Michael Olbrich
2021-05-26 20:32 ` Roland Hieber
2021-05-26 20:41 ` Michael Olbrich [this message]
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=20210526204130.GI28754@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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