Miloslav Trmac wrote:
Steve Dickson napsal(a):
Again.. just fail the open and put the decision of what to do in the
hands of the app... where it belongs...
The application has already _decided_ to crash by using invalid code.
No... glibc made the decision... without give the app any warning
or time to clean up... thats wrong.. imho...
If the code is invalid, how can you expect the application currently has
error handling that _correctly_ handles the case of invalid open ()
invocation? There is no EBACKTOSCHOOL in <errno.h>.
Its not glibc's place (or anybody else) to make such judgments
on the ability of the application or the developer...
steved.
--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers
--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly