Date: Thu, 29 Jan 2004 14:29:45 -0800 (PST) From: "Andrew P. Lentvorski, Jr." <bsder@allcaps.org> To: Frode Nordahl <frode@nordahl.net> Cc: freebsd-current@freebsd.org Subject: Re: rpc.lockd(8) seg faults on 5.2-RELEASE Message-ID: <20040129135653.H21660@mail.allcaps.org> In-Reply-To: <68FC202A-525D-11D8-B122-000A95A9A574@nordahl.net> References: <3DC16400-517B-11D8-9CB2-0005028F6AEB@TrueStep.com> <B6959364-5240-11D8-91E0-000A95A9A574@nordahl.net> <68FC202A-525D-11D8-B122-000A95A9A574@nordahl.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Jan 2004, Frode Nordahl wrote: > Caught a new and different core dump from rpc.lockd today. > > (gdb) bt > #0 dump_filelock (fl=0x809c000) at lockd_lock.c:318 > #1 0x0804e0a1 in lock_nfslock (fl=0x8080815) at lockd_lock.c:875 Your line numbering seems off. You might want to provide a little more context of what line actually failed. ie. line 875 indicates a test_nfslock() call and 318 is an initial function bracket Nonetheless, the reasons for your core dumps elude me. In both cases, the fl should have caused a core dump *before* the line you are indicating. -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040129135653.H21660>