http://bugs.winehq.org/show_bug.cgi?id=7645
Summary: Wine tests fail under FreeBSD and other problems Product: Wine Version: 0.9.32. Platform: PC URL: http://www.freebsd.org OS/Version: FreeBSD Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-binary AssignedTo: wine-bugs@winehq.org ReportedBy: kris@pcbsd.com
I've been working on trying to resolve another issue with WINE & FreeBSD (Bug 3551), and in doing so have run into several other possibly related problems.
Using the latest 0.9.32, I ran "make test" in the main wine tree, and it ran fine for a minute or so, until it reached this point:
../../../tools/runtest -q -P wine -M crypt32.dll -T ../../.. -p crypt32_test.exe .so cert.c && touch cert.ok fixme:crypt:CryptVerifyCertificateSignatureEx unimplemented for NULL signer fixme:crypt:CryptEncodeObjectEx 0: unimplemented
Here it "hung" for almost an hour, with CPU usage at 100% before it finally crashed. Here's what I found in the kernel messages:
Mar 5 11:39:13 pcbsd-8206 kernel: See the i386_set_ldt man page for more info Mar 5 11:39:13 pcbsd-8206 kernel: Warning: pid 91144 used static ldt allocation Mar 5 11:39:13 pcbsd-8206 kernel: See the i386_set_ldt man page for more info Mar 5 11:40:15 pcbsd-8206 kernel: pid 95718 (wine-pthread), uid 0: exited on signal 11
There were a TON of the set_ldt errors reported, before the final crash of wine-pthread. When I run other programs in wine, these set_ldt errors also appear.
I ran across this thread online also, not sure if it'll help in tracking down this error:
http://www.mail-archive.com/freebsd-hackers%40freebsd.org/msg56943.html