From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Arun Sharma <asharma@fb.com>,
Dave Martin <dave.martin@linaro.org>,
linux-perf-users@vger.kernel.org,
Suzuki Poulose <suzuki@in.ibm.com>
Subject: Re: [PATCH] Symbolize stripped binaries without buildid
Date: Wed, 23 Mar 2011 11:23:06 +0530 [thread overview]
Message-ID: <20110323055306.GA4259@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110322212247.GA3594@ghostprotocols.net>
>
> perf symbols: Look at .dymsym again if .symtab not found
>
> The original intent of the code was to repeat the search with
> want_symtab = 0. But as the code stands now, we never hit the "default"
> case of the switch statement. Which means we never repeat the search.
Tested and it works now.
--
Thanks and Regards
Srikar
prev parent reply other threads:[~2011-03-23 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 22:11 [PATCH] Symbolize stripped binaries without buildid Arun Sharma
2011-03-22 21:22 ` Arnaldo Carvalho de Melo
2011-03-23 5:53 ` Srikar Dronamraju [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=20110323055306.GA4259@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=acme@ghostprotocols.net \
--cc=asharma@fb.com \
--cc=dave.martin@linaro.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=suzuki@in.ibm.com \
/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 NNTP newsgroup(s).