From owner-freebsd-current Mon Jul 1 13: 7:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CB3E37B406 for ; Mon, 1 Jul 2002 13:07:48 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13FAB43E13 for ; Mon, 1 Jul 2002 13:07:48 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g61K56Fe028298; Mon, 1 Jul 2002 16:05:06 -0400 (EDT) Date: Mon, 1 Jul 2002 16:05:06 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 1 Jul 2002, Julian Elischer wrote: > > On Mon, 1 Jul 2002, Andrey A. Chernov wrote: > > > On Mon, Jul 01, 2002 at 10:26:22 -0700, Julian Elischer wrote: > > > the question is: > > > did you update both kernel and userland? > > > > This bug is not related to in-kernel KSE code (but, maybe related to > > header files compiled in). I got it even with updated userland and old > > pre-KSE kernel (with both updated I have it too). Only switching to libc_r > > old about month ago helps. > > Ok this is good news becasue it helps narrow the problem. > If an old libc_r runs well it at least suggests that the kernel is > working as it should. That is a great relief to me! > > My current guess is that something in an include file is poisonning the > compile of a new libc_r. > > I think we may need Dan to help us find it.. I'm a few days away from being able to upgrade to the latest -current. I'd suspect that it is something to do with the layout of the fpregs, mcontext or something like that. Libc_r mucks about in jmp_buf (userland) and ucontext/mcontext, so anything that changed those would cause problems. You can enable error checking when compiling libc_r and see if anything comes up too. It should be relatively error free (other than a few _ not being defined). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message