Date: Sun, 18 Jan 2004 14:36:44 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-questions@freebsd.org Subject: Re: rpc.lockd segfault Message-ID: <20040118203644.GA76639@dan.emsphone.com> In-Reply-To: <20040118140539.GA87622@xor.obsecurity.org> References: <200401171338.15670.ajacoutot@lphp.org> <200401172027.19927.ajacoutot@lphp.org> <20040117220110.GB78912@xor.obsecurity.org> <200401181458.44948.ajacoutot@lphp.org> <20040118140539.GA87622@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 18), Kris Kennaway said: > On Sun, Jan 18, 2004 at 02:58:44PM +0100, Antoine Jacoutot wrote: > > > 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). > > > $ gdb /usr/sbin/rpc.lockd > > > How come no debugging symbols are found ? > > > install -s -o root -g wheel -m 555 rpc.lockd /usr/sbin > ^^ > > This strips the debugging symbols. Run gdb against the version of the > binary in the obj/ directory. If you add the -g flag to DEBUG_FLAGS instead of directly to CFLAGS, that will tell the install target not to strip the final binaries (see bsd.prog.mk). -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040118203644.GA76639>