Kirk, Benjamin (JSC-EG311) wrote: > I've seen that too - to be sure we were good i compiled the library without > petsc and verified that laspack was immune from the issue. > > if we report it to the petsc list i imagine it would get pretty low priority > ;-)
It's a libc issue, there's nothing you can do. The docs for getpwuid state | RETURN VALUE | The getpwnam() and getpwuid() functions return a pointer to a passwd structure, or NULL if the matching entry is not found or an error occurs. If an error occurs, | errno is set appropriately. If one wants to check errno after the call, it should be set to zero before the call. | | The return value may point to a static area, and may be overwritten by subsequent calls to getpwent(3), getpwnam(), or getpwuid(). (Do not pass the returned pointer | to free(3).) FWIW, I have glibc-2.10.1 and valgrind-3.5.0 on x86-64 and I do not see this warning. So either valgrind knows that it's spurious, or new libc implements it differently. Jed
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf
_______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
