Fix sem_wait() call in vdd_read()

Introduced in Revision 1.16 (CVS)
Wed May 10 08:52:11 2006 UTC (15 years, 6 months ago) by rswindell

This was supposed to wait (block) until there was a new received
byte (the ringbuf semaphore was signaled), but we were passing the sem_t
value rather than the pointer to the sem_t. Since sem_t (on Windows)
is a HANDLE (which is a void*), there was no compiler warning or
error. Type-safety in C sucks.
So, this just never worked (I'm assuming the call would just fail).

I discovered this bug while working on NTVDMx64 support and in that
case, this call would block/wait forever. Simple one character fix.
14 jobs for master in 15 minutes and 31 seconds (queued for 16 seconds)
Status Job ID Name Coverage
  Build
passed #27660
FreeBSD
jsdoor-freebsd

00:04:29

passed #27661
Linux
jsdoor-linux

00:10:58

passed #27663
FreeBSD
jsdoor-windows

00:02:01

passed #27655
FreeBSD
sbbs-freebsd

00:06:09

passed #27650
Linux
sbbs-linux

00:15:28

passed #27653
Windows
sbbs-windows

00:05:47

passed #27662
FreeBSD
sexpots-freebsd

00:00:35

passed #27651
Linux
sexpots-linux

00:00:29

passed #27654
Windows
sexpots-windows

00:00:39

passed #27658
FreeBSD
syncdraw-freebsd

00:00:49

passed #27659
Linux
syncdraw-linux

00:01:34

passed #27656
FreeBSD
syncterm-freebsd

00:01:31

passed #27652
Linux
syncterm-linux

00:05:12

passed #27657
FreeBSD
syncterm-windows

00:02:16