Re: port-i386/37732 (i386 fork() fails on fs register not being zero; fs register not preserved?)

To: kern-bug-people%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, reinoud%netbsd.org@localhost, reinoud%NetBSD.org@localhost
Subject: Re: port-i386/37732 (i386 fork() fails on fs register not being zero; fs register not preserved?)
From: reinoud%netbsd.org@localhost
Date: Thu, 10 Jan 2008 12:08:02 +0000 (UTC)

Synopsis: i386 fork() fails on fs register not being zero; fs register not 
preserved?

State-Changed-From-To: open->closed
State-Changed-By: reinoud%netbsd.org@localhost
State-Changed-When: Thu, 10 Jan 2008 12:08:01 +0000
State-Changed-Why:
further investigation shows it was suggested by a faulty core dump; following 
the child on gdb shows that its most likely a USER_LDT problem.

Prev by Date: Re: port-i386/37193 (x86 pmap concurrency strategy could use improvement)
Next by Date: Re: kern/37735 (statvfs(2) initially reports empty string instead of '/')
Previous by Thread: kern/37736: Attaching USB devices stops working
Next by Thread: Re: kern/37735 (statvfs(2) initially reports empty string instead of '/')
Indexes:

Home | Main Index | Thread Index | Old Index