Date: Mon, 12 Apr 1999 16:23:56 -0500 From: Dan Nelson <dnelson@emsphone.com> To: "David E. Cross" <crossd@cs.rpi.edu> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ypserv Message-ID: <19990412162356.A42830@dan.emsphone.com> In-Reply-To: <199904121852.OAA22126@cs.rpi.edu>; from "David E. Cross" on Mon Apr 12 14:52:30 GMT 1999 References: <199904121852.OAA22126@cs.rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Apr 12), David E. Cross said: > Our ypserv processes have been dieing a great deal lately (luckily > they restart themselves, but not before all the clients rebind to > another machine). I have tracked the problem down to a stack > corruption. Apparently caused by a stack overflow (I am still > working on it, don't get excited yet ;). I have run into a bit of a > snag with gdb, I do not understand the following when I print out a > function pointer: > > "<functionname+number>" I have found many such references to the > same function, but with different numbers. I am confused as to what > this notation means, I haven't found any reference to it in the gdb > manpage or the gdb "info". It's the offset (in bytes) into a function from a source file not compiled with "-g". gcc can't get line-number information, so it prints the next best thing. The solution is to recompile ypserv with CFLAGS=-g, and make sure you install a non-stripped version. Then gdb will be able to print line number and variable contents from coredumps. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990412162356.A42830>