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: 4109 Reporter: necula Status: closed (set by @damiendoligez on 2007-02-21T13:20:15Z) Resolution: fixed Priority: normal Severity: crash Version: 3.09.2 Fixed in version: 3.09.3 Category: ~DO NOT USE (was: OCaml general) Duplicate of:#4039
Bug description
The functions caml_ml_flush and caml_ml_flush_partial in asmrun/io.c can return without CAMLreturn if they are called on a file that was already closed. This screws up the caml_local_roots data structure, which results in crashes.
Additional information
I am pretty sure that I have filed an identical report a few days ago, and I confirmed that it showed in View Issues. Now I do not see it anymore. If somebody is deleting these reports I expect that they would at least bother to send me email to let me know the reason.
The text was updated successfully, but these errors were encountered:
It was not deleted. It was closed because the bug is fixed.
If you have the same bug in 3.09.3+rc2, I would like to hear about it.
If you try 3.09.3+rc2 and it solves the problem, I would like to
get confirmation.
Original bug ID: 4109
Reporter: necula
Status: closed (set by @damiendoligez on 2007-02-21T13:20:15Z)
Resolution: fixed
Priority: normal
Severity: crash
Version: 3.09.2
Fixed in version: 3.09.3
Category: ~DO NOT USE (was: OCaml general)
Duplicate of: #4039
Bug description
The functions caml_ml_flush and caml_ml_flush_partial in asmrun/io.c can return without CAMLreturn if they are called on a file that was already closed. This screws up the caml_local_roots data structure, which results in crashes.
Additional information
I am pretty sure that I have filed an identical report a few days ago, and I confirmed that it showed in View Issues. Now I do not see it anymore. If somebody is deleting these reports I expect that they would at least bother to send me email to let me know the reason.
The text was updated successfully, but these errors were encountered: