You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 1249 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
It seems that close_channel in io.c does not check the return value of
close(2).
The Linux man page warns that this is potentially the only place where a write
error might get detected (if I understand correctly, when write(2) returns
after
putting data in a buffer but doesn't write it to disk until the file is
closed).
-- Manos
The text was updated successfully, but these errors were encountered:
It seems that close_channel in io.c does not check the return value of
close(2).
I have fixed this in the current working version (3.06+11).
Now Pervasives.close_in and Pervasives.close_out will raise an
exception if the OS signals an error on close.
I have also added close_in_noerr and close_out_noerr for the
very common case when you want to ignore errors.
However, this change may break some programs, so you should be
aware that we might decide to undo it (or find some other solution)
before the next release.
It seems that close_channel in io.c does not check the return value of
close(2).
I have fixed this in the current working version (3.06+11).
Now Pervasives.close_in and Pervasives.close_out will raise an
exception if the OS signals an error on close.
I have also added close_in_noerr and close_out_noerr for the
very common case when you want to ignore errors.
However, this change may break some programs, so you should be
aware that we might decide to undo it (or find some other solution)
before the next release.
-- Damien
Grand merci, oh maître de la librairie réputée standard.
Original bug ID: 1249
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Emmanuel Renieris
Version: CVS
OS: Linux
Submission from: miette.cs.brown.edu (128.148.38.66)
It seems that close_channel in io.c does not check the return value of
close(2).
The Linux man page warns that this is potentially the only place where a write
error might get detected (if I understand correctly, when write(2) returns
after
putting data in a buffer but doesn't write it to disk until the file is
closed).
-- Manos
The text was updated successfully, but these errors were encountered: