public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adam Stylinski <adam.stylinski@etegent.com>
Cc: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Taeung Song <treeze.taeung@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fixed a pathing issue with objdump and grep
Date: Fri, 5 May 2017 09:57:10 -0300	[thread overview]
Message-ID: <20170505125710.GG7891@kernel.org> (raw)
In-Reply-To: <DM5PR06MB32436A790BC9787A6C65E91B9A160@DM5PR06MB3243.namprd06.prod.outlook.com>

Em Wed, May 03, 2017 at 12:12:23PM +0000, Adam Stylinski escreveu:
> The path fed to the argument for objdump used in the perf-annotate
> feature didn't escape spaces. The subsequent argument to grep for
> the name of the DSO containing symbols also assumed no spaces existed
> in the pathname, so grep also parsed these as extra positional
> arguments.

This one didn't apply to tip/perf/urgent, so I tried another patch
addressing the same issue, from Ravi Bangoria, and it applied, ok?

Please take a look at:

 http://lkml.kernel.org/r/20170505101417.2117-1-ravi.bangoria@linux.vnet.ibm.com

- Arnaldo
 
> Signed-off-by: Adam E Stylinski <adam.stylinski@etegent.com>
> ---
>  tools/perf/util/annotate.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
> index 7aa57225cbf7..fc5a96d584f2 100644
> --- a/tools/perf/util/annotate.c
> +++ b/tools/perf/util/annotate.c
> @@ -1441,7 +1441,7 @@ int symbol__disassemble(struct symbol *sym, struct map *map, const char *arch_na
>     snprintf(command, sizeof(command),
>          "%s %s%s --start-address=0x%016" PRIx64
>          " --stop-address=0x%016" PRIx64
> -        " -l -d %s %s -C %s 2>/dev/null|grep -v %s|expand",
> +        " -l -d %s %s -C \"%s\" 2>/dev/null|grep -v \"%s\"|expand",
>          objdump_path ? objdump_path : "objdump",
>          disassembler_style ? "-M " : "",
>          disassembler_style ? disassembler_style : "",
> -- 
> 2.12.2

  reply	other threads:[~2017-05-05 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 12:12 [PATCH] Fixed a pathing issue with objdump and grep Adam Stylinski
2017-05-05 12:57 ` Arnaldo Carvalho de Melo [this message]
2017-05-05 13:22   ` Ravi Bangoria
2017-05-05 13:30     ` Ravi Bangoria

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=20170505125710.GG7891@kernel.org \
    --to=acme@kernel.org \
    --cc=adam.stylinski@etegent.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=borntraeger@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.vnet.ibm.com \
    --cc=treeze.taeung@gmail.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