| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 17 Jun 2010 23:22:57 -0500 From: Tom Zanussi <tzanussi@...il.com> To: Stephane Eranian <eranian@...gle.com> Cc: linux-kernel@...r.kernel.org, peterz@...radead.org, mingo@...e.hu, paulus@...ba.org, davem@...emloft.net, fweisbec@...il.com, acme@...radead.org, perfmon2-devel@...ts.sf.net, eranian@...il.com Subject: Re: [BUG] perf: installed python -report scripts have bogus paths Hi, On Thu, 2010-06-17 at 16:54 +0200, Stephane Eranian wrote: > Hi, > > I was looking at the perf trace and python scripting support. > But I quickly ran into an issue. I compiled with: > $ make prefix=/usr > $ make prefix=/usr install > > All the scripts are installed in /usr/libexec/perf-core/scripts/..... > > The problem is that all the -report scripts have the .py script > paths hardcoded as ~/libexec/..... > > Here is an example with syscall-counts-report > perf trace $@ -s ~/libexec/perf-core/scripts/python/syscall-counts.py $comm > > That should either be stripped to syscall-counts.py and perf trace adds the > prefix or make install needs to patch the path in. Otherwise I don't see how > this can work unless I am confused about the usage model. You're right - it's not a great idea to be hard-coding the path in like this. I'll submit a patch shortly to have perf trace add the prefix. Thanks, Tom -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists