From owner-freebsd-current Wed Oct 14 06:15:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22300 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:15:25 -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 GAA22293 for ; Wed, 14 Oct 1998 06:15:22 -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 IAA02149; Wed, 14 Oct 1998 08:15:01 -0500 (CDT) Message-Id: <199810141315.IAA02149@ns.tar.com> From: "Richard Seaman, Jr." To: "HighWind Software Information" Cc: "current@FreeBSD.ORG" Date: Wed, 14 Oct 98 08:15:01 -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 Tue, 13 Oct 1998 17:30:58 -0400 (EDT), HighWind Software Information wrote: > >After lots of work a few months ago, we got all of our software working >great under FreeBSD 3.0. > >In fact, it STILL works great.. That is, under: > >% uname -a >FreeBSD zonda.highwind.com 3.0-19980831-SNAP FreeBSD 3.0-19980831-SNAP #0: Mon Aug 31 14:03:19 GMT 1998 root@make.ican.net:/usr/src/sys/compile/GENERIC i386 > >However, under the newer FreeBSD's it doesn't seem to work. Our >application goes into 100% user space CPU and makes no progress. [snip] >We are an "aout" binary and have even tried STATICALLY linking with our >libc_r. It still goes into this loop. > >Any ideas what could have happened to cause this. It WAS working fine. Now, >after a little progress, we get into an infinite loop. > >Typhoon uses lots of disk and network I/O. What could we have tripped on? > >Seems to me, statically linking in libc_r would have eliminated any of >the recent changes in libc_r from blame. > >I'm a bit lost as to what to do. I guess we could upgrade our FreeBSD >machine and begin banging our heads against the wall. > >I'm wondering if anyone on this list would have a guess as to what new >changes to the kernel may have caused this. I'm not quite clear about what you're saying. Are you saying that your app, statically linked with a pre Sep 1 libc_r works ok on a pre Sep 1 3.0-current, but that this same statically linked app does not work on newer 3.0-current systems? If so, I'd agree that recent changes to libc_r are probably not the cause of the change in behavior. Are you still doing lots of forks and execs? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message