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: 3995 Reporter: daweil Status: closed (set by @damiendoligez on 2006-08-30T11:13:37Z) Resolution: not a bug Priority: normal Severity: crash Version: 3.08.4 Category: runtime system and C interface
Bug description
I have a segmentation fault very similar to bug #3576, very difficult to reproduce on a small example.
As it happens on a industrial software, I'am not able to send the whole code.
It happens on Win32 version, with both ocaml3.08.3 and ocaml3.08.4, and only when running the bytecode.
The segmentation fault seems to depend on the NAME of the method, maybe when
2 methods have similar names, and when there is many methods in the class.
Are you sure the bug #3576 has been corrected in ocaml3.08.4 ?
The text was updated successfully, but these errors were encountered:
Please close this bug report.
After investigation in our code, it appears that segmentation fault was due to bad C-code that was linked to CAML-code and caused undeterministic side-effect...
Original bug ID: 3995
Reporter: daweil
Status: closed (set by @damiendoligez on 2006-08-30T11:13:37Z)
Resolution: not a bug
Priority: normal
Severity: crash
Version: 3.08.4
Category: runtime system and C interface
Bug description
I have a segmentation fault very similar to bug #3576, very difficult to reproduce on a small example.
As it happens on a industrial software, I'am not able to send the whole code.
It happens on Win32 version, with both ocaml3.08.3 and ocaml3.08.4, and only when running the bytecode.
The segmentation fault seems to depend on the NAME of the method, maybe when
2 methods have similar names, and when there is many methods in the class.
Are you sure the bug #3576 has been corrected in ocaml3.08.4 ?
The text was updated successfully, but these errors were encountered: