From: "thommyj at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/21174] libdw with perf: duplication of entries in callstack
Date: Fri, 17 Feb 2017 14:43:00 -0000 [thread overview]
Message-ID: <bug-21174-10460-WZ5Bkv80oB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21174-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21174
--- Comment #7 from Thommy Jakobsson <thommyj at gmail dot com> ---
Created attachment 9834
--> https://sourceware.org/bugzilla/attachment.cgi?id=9834&action=edit
Add debug printouts in the perf stack unwind
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-02-17 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 6:49 [Bug libdw/21174] New: " thommyj at gmail dot com
2017-02-17 9:11 ` [Bug libdw/21174] " mark at klomp dot org
2017-02-17 9:39 ` thommyj at gmail dot com
2017-02-17 9:47 ` thommyj at gmail dot com
2017-02-17 10:07 ` mark at klomp dot org
2017-02-17 10:16 ` mark at klomp dot org
2017-02-17 14:42 ` thommyj at gmail dot com
2017-02-17 14:43 ` thommyj at gmail dot com [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=bug-21174-10460-WZ5Bkv80oB@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).