Issue with classType on CompiledCode

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue with classType on CompiledCode

Ron Teitelbaum
Hi All,

Ran into a problem trying to load the subclass of ByteArray

CompiledCode

from Monticello Configuration.  

It was stored with a typeOfClass of #data but CompiledCode returns typeOfClass #compiledMethod.

I'm getting the error: 

CompiledCode cannot be recompiled

from 

Classbuilder >> validateSubclassFormat: newType from: oldClass forSuper: newSuper extra: newInstSize.

Suggestions on how to fix this or should we 
1) allow #data to #compiledMethod to succeed the validation?
2) Manually fix it and commit a new configuration.

Also I see that there are two updates on trunk.  

update and 
update.spur 

Which configuration are we using?  Why are there two?

Thanks for your help!!

Ron Teitelbaum 


Reply | Threaded
Open this post in threaded view
|

Re: Issue with classType on CompiledCode

Eliot Miranda-2
Hi Ron,


On Jul 18, 2020, at 11:28 AM, Ron Teitelbaum <[hidden email]> wrote:


Hi All,

Ran into a problem trying to load the subclass of ByteArray

CompiledCode

from Monticello Configuration.  

It was stored with a typeOfClass of #data but CompiledCode returns typeOfClass #compiledMethod.

I'm getting the error: 

CompiledCode cannot be recompiled

from 

Classbuilder >> validateSubclassFormat: newType from: oldClass forSuper: newSuper extra: newInstSize.

Suggestions on how to fix this or should we 
1) allow #data to #compiledMethod to succeed the validation?
2) Manually fix it and commit a new configuration.

I would look at specific changes to Monticello that allow CompiledMethod to load.  I believe there is no problem in current trunk.  You and I could take a look at this together tmrw.


Also I see that there are two updates on trunk.  

update and 
update.spur 

Which configuration are we using? 

update

Why are there two?

update.spur is historical and was required as we transitioned to Spur from 4.5 to 4.6.


Thanks for your help!!

Ron Teitelbaum