From: Mark Wielaard <mark@klomp.org>
To: Ulf Hermann <ulf.hermann@qt.io>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH v2] Add frame pointer unwinding for aarch64
Date: Tue, 25 Apr 2017 12:40:00 -0000 [thread overview]
Message-ID: <1493045634.31726.25.camel@klomp.org> (raw)
In-Reply-To: <1b3a1a6b-5ea2-e6c1-e555-0034b7d43e57@qt.io>
On Thu, 2017-04-20 at 14:41 +0200, Ulf Hermann wrote:
> diff --git a/tests/backtrace.aarch64.fp.core.bz2 b/tests/backtrace.aarch64.fp.core.bz2
> new file mode 100644
> index 0000000..ef628af
> Binary files /dev/null and b/tests/backtrace.aarch64.fp.core.bz2 differ
> diff --git a/tests/backtrace.aarch64.fp.exec.bz2 b/tests/backtrace.aarch64.fp.exec.bz2
> new file mode 100755
> index 0000000..69ba887
> Binary files /dev/null and b/tests/backtrace.aarch64.fp.exec.bz2 differ
I got these separately. I assume they are as in the email you sent on
Mon, 10 Apr 2017 14:48:06 +0200 (which didn't hit the list because it
had the binaries attached...)
I'll but them on my mjw/fp-unwind branch (which I am rewriting
currently, not pushed yet).
> diff --git a/tests/run-backtrace-fp-core-aarch64.sh b/tests/run-backtrace-fp-core-aarch64.sh
> +# The binary is generated by compiling backtrace-child without debug
> +# information, but with -fno-omit-frame-pointer.
> +#
> +# gcc -static -O2 -fno-omit-frame-pointer -D_GNU_SOURCE \
> +# -pthread -o backtrace.aarch64.fp.exec backtrace-child.c \
> +#
> +# Then strip the .eh_frame and .eh_frame_hdr sections from the binary:
> +#
> +# strip -R .eh_frame backtrace.aarch64.fp.exec
> +# strip -R .eh_frame_hdr backtrace.aarch64.fp.exec
> +#
> +# The core is generated by calling the binary with --gencore
This description doesn't seem to match anymore. Should this be:
# The binary is generated by compiling with eh_frame CFI, but with frame
# pointers.
#
# gcc -static -O2 -fno-omit-frame-pointer -fno-asynchronous-unwind-tables \
# -D_GNU_SOURCE -pthread -o tests/backtrace.x86_64.fp.exec -I. -Ilib \
# tests/backtrace-child.c
#
# The core is generated by calling the binary with --gencore
Thanks,
Mark
next prev parent reply other threads:[~2017-04-24 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 12:41 Ulf Hermann
2017-04-25 12:40 ` Mark Wielaard [this message]
2017-04-25 12:50 ` Ulf Hermann
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=1493045634.31726.25.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=ulf.hermann@qt.io \
/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).