From: Paul Smith <paul@mad-scientist.net>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: Writing core files to contain buildids
Date: Wed, 28 Oct 2020 00:40:44 -0400 [thread overview]
Message-ID: <faab4a1bce8d9eaf13015de88373da7f70cebc9e.camel@mad-scientist.net> (raw)
In-Reply-To: <20201027222329.GC2691@wildebeest.org>
On Tue, 2020-10-27 at 23:23 +0100, Mark Wielaard wrote:
> Do you have the generated core files somehwere so others can look at
> them? How exactly are you testing the build-id notes are there?
I don't have one to publish but I can create one. That's a good idea
anyway as it will be simpler to debug than the actual system which is
much more complex.
I'm using eu-unstrip -n --core core.xxx to check for build IDs.
next prev parent reply other threads:[~2020-10-28 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 7:06 Paul Smith
2020-10-27 14:39 ` Mark Wielaard
2020-10-27 20:20 ` Paul Smith
2020-10-27 22:23 ` Mark Wielaard
2020-10-28 4:40 ` Paul Smith [this message]
2020-10-28 10:01 ` Mark Wielaard
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=faab4a1bce8d9eaf13015de88373da7f70cebc9e.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).