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: 4442 Reporter: adamc Assigned to:@damiendoligez Status: closed (set by @damiendoligez on 2007-11-20T18:54:39Z) Resolution: fixed Priority: normal Severity: crash Version: 3.10+dev Fixed in version: 3.10+dev Category: ~DO NOT USE (was: OCaml general) Monitored by: adamc ertai @alainfrisch
Bug description
Starting from a large program with many dependencies that began segfaulting unpredictably shortly after we added use of weak pointers, I have come up with a one-page example that reliably triggers a segmentation fault (or other nasty fault) with 3.10.1+dev0 on both ia32 and amd64 Linux. Making small changes like manual inlining of functions changes whether or not the crash occurs, so I think it is almost certain that memory corruption is occurring.
Original bug ID: 4442
Reporter: adamc
Assigned to: @damiendoligez
Status: closed (set by @damiendoligez on 2007-11-20T18:54:39Z)
Resolution: fixed
Priority: normal
Severity: crash
Version: 3.10+dev
Fixed in version: 3.10+dev
Category: ~DO NOT USE (was: OCaml general)
Monitored by: adamc ertai @alainfrisch
Bug description
Starting from a large program with many dependencies that began segfaulting unpredictably shortly after we added use of weak pointers, I have come up with a one-page example that reliably triggers a segmentation fault (or other nasty fault) with 3.10.1+dev0 on both ia32 and amd64 Linux. Making small changes like manual inlining of functions changes whether or not the crash occurs, so I think it is almost certain that memory corruption is occurring.
File attachments
The text was updated successfully, but these errors were encountered: