search

zinonet / naclports

Automatically exported from code.google.com/p/naclports
0 stars 0 forks source link

nacl_io shouldn't return EINVAL for send(x,0,0) #228

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
nacl_io currently agressively returns a EINVAL for a number of cases where a 
null pointer is passed. This may be fine for calls expected to receive data, 
but is unusual for call like send(), which might be passed a null buffer but 
zero length.
(Example: libxcb's writev polyfill).
We should be able to tolerate this case.

Original issue reported on code.google.com by bradnelson@google.com on 15 Jul 2015 at 12:09