From: Rick K. <rk...@nc...> - 2006-12-01 19:30:36
|
miwei, I have had a chance to build PAPI 3.5.0 on a Xeon workstation and test it with PerfSuite. I'm able to confirm failures similar to what you reported. The problem seems to arise when profiling, and the failure is due to an error return from PAPI of PAPI_EINVAL, which means PAPI thinks it has received an invalid argument to one of its library routines. This doesn't happen in all uses of profiling, but does as you point out, and it happens consistently. I'm not sure at this point whether the problem is in PerfSuite or in PAPI 3.5.0 but will continue to investigate. I have a couple of suggestions in the meantime: 1. Use the latest PerfSuite 0.6.2 version, not 0.6.1 which is now rather old. This won't fix the immediate problem but has many fixes and enhancements that have been implemented. 2. Consider installing PAPI 3.2.1 in addition to 3.5.0 (place it in a different directory) and try using PerfSuite with that. This combination should be quite stable. Sorry for the problems, will post when I know more... Rick >> I run "make check" after perfsuite has been installed, but several fail >> occurs. The tests to >> papi and tdom works well after their installation. What 's wrong with it? >> The testsuite.log >> is attached. >> Thanks for help >> >> -- |