From owner-freebsd-current Tue Oct 13 15:13:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07319 for freebsd-current-outgoing; Tue, 13 Oct 1998 15:13:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07309 for ; Tue, 13 Oct 1998 15:13:09 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id SAA07558; Tue, 13 Oct 1998 18:12:16 -0400 (EDT) Date: Tue, 13 Oct 1998 18:12:16 -0400 (EDT) Message-Id: <199810132212.SAA07558@highwind.com> From: HighWind Software Information To: jb@cimlogic.com.au CC: current@FreeBSD.ORG In-reply-to: <199810132200.IAA05333@cimlogic.com.au> (message from John Birrell on Wed, 14 Oct 1998 08:00:27 +1000 (EST)) Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Hmm. Wouldn't statically linking OUR local libc_r into the application make it so the changes to libc_r at the customer site not effect us? Maybe I am missing something. 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. Can you review how to do that thread status dump again? I apologize for my ignorance. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message