Hello,
in GS/S 64bit 3.0 and 3.1 sending dynamicInstVarAt: to special objects like nil, true, false or SmallIntegers crashes the gem with
> Gemstone Signal Handler: Signal 11, SIGSEGV Received
As long as primitive 881 is not more robust or the problematic classes have guard implementations like IdentityBtreeNode one must take care to check the receivers of that message.
BTW the methods dynamicInstanceVariables and dynamicInstVarAt:put: handle these edge cases properly.
Kind regards
Georg
--
GemStone-Smalltalk mailing list
Unsubscribe: send e-mail with the word "unsubscribe" in body (without quotes) to:
[hidden email]
Archive:
http://forum.world.st/Gemstone-Customers-f1461796.html