Bug 45586

GemStone/S 64 Bit

3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2

Possible SEGV on execution of method upgraded from 3.1.x and not recompiled

There are minor changes in the bytecode generated from method compliation in v3.1.x and 3.2.x, related to the changes that allow a step point at the beginning of a method.

A case has been observed in which a SEGV in a Gem is apparently related to this  difference in the bytecodes. While this is a very rare situation and is not believed to be at risk for causing any other problems, for reliability it is recommended that all application methods be recompiled as part of the 3.1.x to 3.2.x upgrade process.

Workaround

Recompile the method.


Last updated: 12/11/15