On Thu, May 20, 2010 at 8:59 AM, Tianwei <tianwei.sh...@gmail.com> wrote: > Hi, Stephane, > I try to analyze the overhead of a Pin tool, I used the following command, > but failed: > tian...@tianwei:~/valgrind/drt/tsan$ pfmon /home/tianwei/pin/pin > -follow_execv -t64 ./bin/amd64-linux-debug-ts_pin.so -t > ./bin/x86-linux-debug-ts_pin.so -short_name -slow_asserts -- > ../unittest/bin/demo_tests-linux-amd64-O0 --gtest_filter=*Race* > [23085] task terminated by signal 10, results may be incorrect > 4808773 UNHALTED_CORE_CYCLES > E:Attach to pid 23085 failed: Operation not permitted > There may be some issues with ptrace. The current pfmon code stills uses ptrace to attach/detach from a task. Pin may already be using ptrace.
I suggest you try with perf_events and the perf tool, see if you have more luck. > Currently I am still not very clear with Pin, but is there any specially > flag I need to add in order to monitor Pin with pfmon. I read the Pin > documents, the three components of Pin (Pin engine, Pin tool, user > application) should locate in the same address space, I do not know what's > the special thing there. > Thanks. > Tianwei > -- > Sheng, Tianwei > Inst. of High Performance Computing > Dept. of Computer Sci. & Tech. > Tsinghua Univ. > > ------------------------------------------------------------------------------ > > > _______________________________________________ > perfmon2-devel mailing list > perfmon2-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/perfmon2-devel > > ------------------------------------------------------------------------------ _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
