Date: Tue, 5 Mar 2002 23:03:36 -0700 (MST) From: Tony Arcieri <tarcieri@atmos.colostate.edu> To: freebsd-hackers@freebsd.org Subject: aio_read() oddness Message-ID: <20020305225908.U48034-100000@rylos.atmos.colostate.edu>
next in thread | raw e-mail | index | archive | help
I'm not currently subscribed to this list, so please cc replies to me. I was playing around with aio_read() and ran into some seemingly aberrant behavior, although not with aio_read() itself, but the resulting signal. Within struct aiocb I was setting: aio_sigevent.sigev_notify = SIGEV_SIGNAL; aio_sigevent.sigev_value.sigval_int = 42; iocb.aio_sigevent.sigev_signo = SIGUSR1; Then in the sigaction structure: sa_flags = SA_SIGINFO; Upon completion of the requested read, a signal is sent. Within the siginfo structure, si_signo is set properly. However, si_value.sigval_int is zero. Is this just not implemented completely yet or am I missing something? Tony Arcieri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020305225908.U48034-100000>