From owner-freebsd-stable Fri Nov 17 8:58:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DB55C37B4C5 for ; Fri, 17 Nov 2000 08:58:08 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA01839; Fri, 17 Nov 2000 08:58:05 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eAHGw4x57520; Fri, 17 Nov 2000 08:58:04 -0800 (PST) (envelope-from jdp) Date: Fri, 17 Nov 2000 08:58:04 -0800 (PST) Message-Id: <200011171658.eAHGw4x57520@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Reply-To: stable@freebsd.org Cc: jkh@winston.osd.bsdi.com Subject: Re: libc shlib version In-Reply-To: <45706.974318388@winston.osd.bsdi.com> References: <45706.974318388@winston.osd.bsdi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <45706.974318388@winston.osd.bsdi.com>, Jordan Hubbard 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 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