From: Ryan Heniser <ryan.heniser@rsp.com.au>
To: linux-perf-users@vger.kernel.org
Subject: My options when vendor refuses to supply debug symbols
Date: Thu, 5 Nov 2015 05:14:18 +0000 (UTC) [thread overview]
Message-ID: <loom.20151105T061223-246@post.gmane.org> (raw)
What options do we have when a third party vendor refuses to provide debug
symbols because they fear it might leak IP? There code is compiled into one
dynamic shared object. Is there a way to perf record the memory addresses
such that I could pass them on to the company for them to convert to function
signatures?
Kind regards,
Ryan
next reply other threads:[~2015-11-05 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 5:14 Ryan Heniser [this message]
2015-11-09 15:17 ` My options when vendor refuses to supply debug symbols Arnaldo Carvalho de Melo
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=loom.20151105T061223-246@post.gmane.org \
--to=ryan.heniser@rsp.com.au \
--cc=linux-perf-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.