On Sat, Jan 17, 2009 at 4:05 AM, Francois Gouget fgouget@free.fr wrote:
On Fri, 16 Jan 2009, Austin English wrote: [...]
Haven't been able to test real apps yet :-).
I'm assuming you want me to test using, e.g., cpu-z?
I was thinking more of checking the traces. It looks like dlls/kernerl32/tests/thread.c (and a couple of others) call GetSystemInfo(), which should be sufficient to check the +reg traces (+reg? WTH?).
-- Francois Gouget fgouget@free.fr http://fgouget.free.fr/ In theory, theory and practice are the same, but in practice they're different.
bash-3.2$ make thread.ok ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so thread.c && touch thread.ok err:process:__wine_kernel_init boot event wait timed out assertion "thread->pt_blockgen == thread->pt_unblockgen" failed: file "/home/builds/ab/netbsd-4-0-1-RELEASE/src/lib/libpthread/pthread_lock.c", line 195, function "pthread_spinlock" assertion "thread->pt_blockgen == thread->pt_unblockgen" failed: file "/home/builds/ab/netbsd-4-0-1-RELEASE/src/lib/libpthread/pthread_lock.c", line 195, function "pthread_spinlock" *** Error code 1
Stop. make: stopped in /home/austin/wine-git/dlls/kernel32/tests
Haven't found a fix for that one yet. They've got a patch in their port to use use wine-kthread by default, but doesn't seem to help.