Re: 5 Wine-Tests fail on FreeBSD 5.1

2003-08-15 Thread Eric Pouech
I think more that's a discrepency in OSS handling between linux & *BSD (or a more subtle bug somewhere) could you rerun with WINEOPTIONS="-debugmsg +wave,+dsound,+wavemap" back from vacation... the trace only shows a decent startup and a wait for incoming audio packets, which never show up. Let'

Re: 5 Wine-Tests fail on FreeBSD 5.1

2003-07-16 Thread Eric Pouech
The Backtrace now looks like this: (gdb) bt #0 0x5c236783 in read () from /usr/lib/libc.so.5 #1 0x5c0b11ee in wait_reply (cookie=0x5d252d44) at ../../include/winnt.h:1622 #2 0x5c0b1483 in NTDLL_wait_for_multiple_objects (count=1, handles=0x5d252e10, flags=4, timeout=0x0) at sync.c:580 #3 0

Re: 5 Wine-Tests fail on FreeBSD 5.1

2003-07-15 Thread Eric Pouech
Ulrich Spoerlein wrote: Now what exactly is this code waiting for? Why doesn't it get any data from fd 12? (And what are fds 12 and 13 (msg_pipe[0] and msg_pipe[1] anyway)? the pipe is used to synchronize messages between the main thread (the one which sends data to be played) and the player threa