This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/13740] lio_listio: when pass aiocb with a invalid aio_lio_opcode, __error_code is not set
- From: "carlos at systemhalted dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 28 Feb 2012 16:16:02 +0000
- Subject: [Bug libc/13740] lio_listio: when pass aiocb with a invalid aio_lio_opcode, __error_code is not set
- Auto-submitted: auto-generated
- References: <bug-13740-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13740
--- Comment #4 from Carlos O'Donell <carlos at systemhalted dot org> 2012-02-28 16:16:02 UTC ---
Kai,
I'm looking for a test case that shows that glibc does not return an error code
on invalid input. In your example the input is invalid, and the return is
correct EINVAL=22.
The test case should return 0 if it passes e.g. You passed in an invalid value
and got back the correct error code.
The test case should return 1 if it fails e.g. you passed in an invalid value
and got back no error code or the wrong error code.
Does that help clarify what I'm looking for?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.