On Tue, 29 Sep 2009, 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 > ;-) Low priority until we could confirm that it wasn't a bug in our PETSc interface, yeah. But they've got some excellent programmers there, and I suspect they'd take even a small memory leak seriously. When I sent them a feature request of "have you considered adding long double support?" years ago, it took them no time at all to go from "that's a good idea" to "you'll need to use a C BLAS, but it works now". --- Roy ------------------------------------------------------------------------------ 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
