Date: Wed, 14 Oct 1998 08:00:27 +1000 (EST) From: John Birrell <jb@cimlogic.com.au> To: info@highwind.com (HighWind Software Information) Cc: current@FreeBSD.ORG Subject: Re: Recent 3.0's are Depressing Message-ID: <199810132200.IAA05333@cimlogic.com.au> In-Reply-To: <199810132130.RAA06806@highwind.com> from HighWind Software Information at "Oct 13, 98 05:30:58 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
HighWind Software Information wrote: > 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. The recent changes mostly affect signal handling with sigwait(). There was one change to the thread kernel, but I doubt that would be a problem. I don't see what a static link would buy you compared to a dynamic one. I also don't see what this has to do with the FreeBSD kernel since this is a user-space thread implementation. I suggest that you use CVSup's cvs mode to track the cvs repository and then checkout sources based on date to isolate which changes have bitten you. There are test programs in the tree that were submitted by the author of the signal handling changes. You should try to duplicate your problem using those tests. Providing a ktrace without a thread status dump is useless IMO. All that you've shown is that the thread scheduler can't find a thread to run. The thread status dump should tell you why. I explained that to you many months ago. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810132200.IAA05333>