Philip J. Mucci wrote:
Ok, I found the memory information error and fixed it in CVS, but the
next error is troubling and it is due to the way we handle umasked
events in PAPI. It fails on AMD because the first event has a umask.
I have fixed the core dump though.
I'm attempting a fix now. Can you give her another spin? let me know how
it goes.
Thanks
Did a cvs update.
strstr() returns a pointer if it is successful and NULL if there is NO match.
The attached patch should do the correct thing.
Still get the following error when trying papi_command_line:
$ ./utils/papi_command_line PAPI_TOT_CYC
Successfully added: PAPI_TOT_CYC
PAPI Error: pfm_write_pmcs(3,0x2ba7cbd3c110,1): not supported.
PAPI Error: Error Code -3,PAPI_ESYS,A System/C library call failed: Invalid
argument.
command_line.c FAILED
Line # 64
System error in PAPI_start: Invalid argument
-Will
Index: perfmon.c
===================================================================
RCS file: /cvs/homes/papi/papi/src/Attic/perfmon.c,v
retrieving revision 1.1.2.34
diff -u -r1.1.2.34 perfmon.c
--- perfmon.c 29 Oct 2006 14:28:07 -0000 1.1.2.34
+++ perfmon.c 31 Oct 2006 15:57:52 -0000
@@ -121,7 +121,7 @@
{
if (strcasecmp(s,"GenuineIntel") == 0)
*vendor = PAPI_VENDOR_INTEL;
- else if (strstr(s,"AMD") == 0)
+ else if (strstr(s,"AMD") != 0)
*vendor = PAPI_VENDOR_AMD;
else if (strcasecmp(s,"IBM") == 0)
*vendor = PAPI_VENDOR_IBM;
_______________________________________________
perfmon mailing list
[email protected]
http://www.hpl.hp.com/hosted/linux/mail-archives/perfmon/
