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: 5704 Reporter:@lefessan Status: closed (set by @alainfrisch on 2013-07-09T11:12:44Z) Resolution: fixed Priority: normal Severity: trivial Version: 4.00.0 Target version: 4.01.0+dev Fixed in version: 4.01.0+dev Category: back end (clambda to assembly) Monitored by:@glondu@mmottl
Bug description
It looks like cmx magic numbers have not been changed since commit 7812, but last changes to the Clambda.ulambda (used for inlined function code in .cmx) have commit numbers 11007 and 12179.
Some people have noticed segfaults of ocamlopt/ocamlopt.opt due to heap corruption. Is it possible that these segfaults come from .cmx files of older versions ? (I open this bug report so that such problems can be linked to this bug report as a possible cause)
The text was updated successfully, but these errors were encountered:
I agree that updating the magic numbers wouldn't hurt. On the other hand, I don't think magic number confusion is causing the heap corruption in question --- #5757 looks like a more likely culprit. So, I propose to schedule this update for 4.01 and leave it out of the bugfix release 4.00.1.
Original bug ID: 5704
Reporter: @lefessan
Status: closed (set by @alainfrisch on 2013-07-09T11:12:44Z)
Resolution: fixed
Priority: normal
Severity: trivial
Version: 4.00.0
Target version: 4.01.0+dev
Fixed in version: 4.01.0+dev
Category: back end (clambda to assembly)
Monitored by: @glondu @mmottl
Bug description
It looks like cmx magic numbers have not been changed since commit 7812, but last changes to the Clambda.ulambda (used for inlined function code in .cmx) have commit numbers 11007 and 12179.
Some people have noticed segfaults of ocamlopt/ocamlopt.opt due to heap corruption. Is it possible that these segfaults come from .cmx files of older versions ? (I open this bug report so that such problems can be linked to this bug report as a possible cause)
The text was updated successfully, but these errors were encountered: