Date: Sat, 17 Jan 2004 14:01:11 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Antoine Jacoutot <ajacoutot@lphp.org> Cc: freebsd-questions@freebsd.org Subject: Re: rpc.lockd segfault Message-ID: <20040117220110.GB78912@xor.obsecurity.org> In-Reply-To: <200401172027.19927.ajacoutot@lphp.org> References: <200401171338.15670.ajacoutot@lphp.org> <200401172027.19927.ajacoutot@lphp.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--OwLcNYc0lM97+oe1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 17, 2004 at 08:27:19PM +0100, Antoine Jacoutot wrote: > On Saturday 17 January 2004 13:38, Antoine Jacoutot wrote: > > I'm having a problem under FreeBSD-5.2-RELEASE. > > I mount my users homedir under NFS and need rpc.lockd. > > Unfortunately, and with no reason nor log, rpc.lockd regularly core dum= p... > > Any idea where I should start looking. >=20 > Here is more information about my problem, using gdb on thecore file: Unfortunately that doesn't give any information. You'll need to recompile rpc.lockd with GDB debugging symbols (add -ggdb to CFLAGS). See the developer's handbook on the website for more information about debugging program failures with gdb (specifically, how to obtain a useful backtrace). Kris --OwLcNYc0lM97+oe1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFACbCmWry0BWjoQKURAseFAJ9kkYFVbuLIaT/p0se9xllaFAJEYgCgjSsa 4jvi5jGG/OXqdojJpJmNbTE= =F+sd -----END PGP SIGNATURE----- --OwLcNYc0lM97+oe1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040117220110.GB78912>