Date: Fri, 17 Nov 2000 08:58:04 -0800 (PST) From: John Polstra <jdp@polstra.com> To: stable@freebsd.org Cc: jkh@winston.osd.bsdi.com Subject: Re: libc shlib version Message-ID: <200011171658.eAHGw4x57520@vashon.polstra.com> In-Reply-To: <45706.974318388@winston.osd.bsdi.com> References: <45706.974318388@winston.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <45706.974318388@winston.osd.bsdi.com>, Jordan Hubbard <jkh@winston.osd.bsdi.com> wrote: > > Maybe I'm crazy, but can't we find and kill the API change that caused > > this and back it out for 4.x? I suspect it was the per interface stat > > changes in the network code, but I could very well be wrong. > > It seems to be a great mystery - I'm still not sure myself just what > the heck changed. Well for cryin' out loud, all it takes is for somebody who is experiencing the problem to run the failing program under ktrace! All the failures are SIGSYS. Look at the ktrace output and see what non-existent system call is being called. (Hint: find the system call number in -current or -stable's <sys/sycall.h> file.) Then grep through -stable's libc sources and find out what's calling it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011171658.eAHGw4x57520>