[OpenAFS-devel] valgrind and openafs...

[Neulinger, Nathan]

FYI, found one issue with valgrind and LWP... If you want any useful
results, prior to starting the process with valgrind, you need to
"setenv AFS_LWP_STACK_SIZE 1000000". Anything less than 1 MB it thinks
it's not a different stack and it's memory allocated on the same stack.
That makes the reports a lot quieter, so far mainly just memory leaks.=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Derrick J Brashear [mailto:shadow@dementia.org]=20
> Sent: Tuesday, April 15, 2003 12:20 AM
> To: openafs-devel@openafs.org
> Subject: RE: [OpenAFS-devel] valgrind and openafs...
>=20
>=20
> On Mon, 14 Apr 2003, Neulinger, Nathan wrote:
>=20
> > trying to track...
> >
> > My head cvs fileserver runs fine on a test box, but when I=20
> get it under
> > real load, I get a segfault after a few minutes.
>=20
> Do you get any log messages? A vaguely useful backtrace?
>=20
> Note that a while ago I posted a point to a linux kernel patch which
> causes pthreaded binaries to drop a useful core.
>=20
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20