> One of the problems had to do with a member of a member being stored to
> or something bad like that. It's quite possible that ugen.c was trashing
> very random locations in kernel memory every time the bogus code was hit.
Highly unlikely.  It would only happen if you opened an ugen device
and then did a select on it.

    -- Lennart