Date: Mon, 1 Jul 2002 16:50:35 -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.10207011645540.4438-100000@pcnet1.pcnet.com> In-Reply-To: <Pine.BSF.4.21.0207011321250.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: > I don't change any of those. > > On Mon, 1 Jul 2002, Daniel Eischen wrote: > > > > 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. > > > > > It's still unclear if a KSE kernel works with an old libc_r or visa versa. > > I'd like to see if a new libc_r works with an old kernel (someone who can > boot kernel.back and test...) > > to check if you have a non KSE kernel, > sysctl kern.threads will only succeed in a new kernel. I also made changes to uthread_sigpending.c and uthread_sigsuspend.c 3 days ago (lib/libc_r/uthread/...). You can try reverting those changes and go back to revisions 1.18 and 1.11 respectively. -- 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.10207011645540.4438-100000>