Date: Mon, 1 Jul 2002 16:05:06 -0400 (EDT) From: Daniel Eischen <eischen@pcnet1.pcnet.com> To: Julian Elischer <julian@elischer.org> Cc: "Andrey A. Chernov" <ache@nagual.pp.ru>, NAKAJI Hiroyuki <nakaji@boggy.acest.tutrp.tut.ac.jp>, freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r Message-ID: <Pine.GSO.4.10.10207011556130.26890-100000@pcnet1.pcnet.com> In-Reply-To: <Pine.BSF.4.21.0207011215390.91887-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 _<function-names> not being defined). -- Dan Eischen 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?Pine.GSO.4.10.10207011556130.26890-100000>