Ticket #976 (closed enhancement: fixed)
class redefinition after snap-reader-methods causes invalid memory operation
|Reported by:||fare||Owned by:||gb|
I haven't been able to reduce that to a small runnable example yet, but when we compile our application with (ccl::snap-reader-methods :known-sealed-world t)
If we subsequently re-define a class, even identically, some existing methods using that class will fail with an "Invalid memory operation". That's with 1.8-r15359 LinuxX8664. Before the patch from http://trac.clozure.com/ccl/changeset/14968 was used, it was a plain crash.
Can CCL be patched so that any class-redefinition after snap-reader-methods would invalidate the snapped reader methods, and possibly issue a warning or continuable error (since a promise was broken)?
Xref: ITA bug 105557
- Summary changed from class redefinition after snap-reader-methods causes to class redefinition after snap-reader-methods causes invalid memory operation
- Status changed from assigned to closed
- Resolution set to fixed