Tom Hughes wrote: > Michael Abshoff wrote: Hi Tom,
>> I am running the 3.4.0 release on a 64 bit Ubuntu box. While running >> the linbox (linalg.org) test suite under ptr-check I am seeing the >> following: > > Can you please raise a bug for this in bugzilla... Actually you might > want to check the existing bugs first as I think somebody may already > have reported this, but without the syscall number. If that is the case > then just adding the syscall number would be good. > > I assume this is a 64 bit x86 program? In which case the syscall is > getrusage. I just played around a little more and discovered another unsupported syscall when running chown, i.e. mabsh...@sage:~/build/linbox-testing/linbox-svn3066/tests/foo$ ~/build/eMPIRe/sage-3.2.3.final/local/bin/valgrind --tool=exp-ptrcheck chown mabshoff:mabshoff TODO ==2132== exp-ptrcheck, a heap, stack & global array overrun detector. ==2132== NOTE: This is an Experimental-Class Valgrind Tool. ==2132== Copyright (C) 2003-2008, and GNU GPL'd, by OpenWorks Ltd et al. ==2132== Using LibVEX rev 1878, a library for dynamic binary translation. ==2132== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP. ==2132== Using valgrind-3.4.0, a dynamic binary instrumentation framework. ==2132== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al. ==2132== For more details, rerun with: -v ==2132== sysno == 262 I have appended the remaining info to https://bugs.kde.org/show_bug.cgi?id=179618 > Tom I am willing to test a bunch of shell utilities and code to find more syscalls that are missing, but should I open individual tickets for each syscall or stuff them onto the existing ticket? Cheers, Michael ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
