From owner-freebsd-current Wed Oct 14 08:53:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10355 for freebsd-current-outgoing; Wed, 14 Oct 1998 08:53:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10332 for ; Wed, 14 Oct 1998 08:53:06 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id KAA02913; Wed, 14 Oct 1998 10:52:42 -0500 (CDT) Message-Id: <199810141552.KAA02913@ns.tar.com> From: "Richard Seaman, Jr." To: "Brian Tao" Cc: "current@FreeBSD.ORG" Date: Wed, 14 Oct 98 10:52:42 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Oct 1998 10:00:18 -0400 (EDT), Brian Tao wrote: > > I believe that is what they have tried with beta testers. I've >seen the same problem with binary dynamically linked to >/usr/lib/aout/libc_r.so.3.0, the library dated Oct 1 (the last time I >did a make world without -DNOAOUT). I'm going to try backing down >just the a.out libc_r to Aug 31 or so to see what the effects are. I'd be curious if the problem still exists with a libc_r that is completely up to date. There were some changes to the thread scheduler after October 1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message