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: 238 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
The error causes the serialization to miscompute the size of the block to
allocate when reading the data back in.
Bug 2:
byterun/intern.c:266
if (intern_obj_table != NULL) intern_obj_table[obj_counter++] = v;
Custom objects (e.g. int64) were not put into the shared lookup table, and the
object count was not correctly maintained. This causes problems when
deserializing shared custom objects.
Simplest example to exhibit bug: write a tuple (i,i), where i is an int64 to a
file with output_value. On input_value, the second component is a garbage
pointer.
The text was updated successfully, but these errors were encountered:
Original bug ID: 238
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Manuel Fahndrich
Version: 3.00
OS: Win2K
Submission from: tide72.microsoft.com (131.107.3.72)
I found two errors in the serialization code, one related to int64's in
particular, the other for all custom objects.
Bug 1:
byterun/ints.c:282
<
*wsize_64 = *wsize_64 = 8;
*wsize_32 = *wsize_64 = 8;
The error causes the serialization to miscompute the size of the block to
allocate when reading the data back in.
Bug 2:
byterun/intern.c:266
if (intern_obj_table != NULL) intern_obj_table[obj_counter++] = v;
Custom objects (e.g. int64) were not put into the shared lookup table, and the
object count was not correctly maintained. This causes problems when
deserializing shared custom objects.
Simplest example to exhibit bug: write a tuple (i,i), where i is an int64 to a
file with output_value. On input_value, the second component is a garbage
pointer.
The text was updated successfully, but these errors were encountered: