Bug 47409

GemStone/S 64 Bit

3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.1, 3.3, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8, 3.2.7, earlier versions

3.4.2

performOnServer: blocked SIGTERM

During the vfork() call invoked by System class >> performOnServer:, all signals are blocked (this was done to avoid a deadlock).  If a third party software package relies on these signals, it will not operate correctly when invoked from GemStone Smalltalk code.

In versions in which this bug is fixed, SIGTERM is no longer blocked, though other signals still are.  If other signals are required, contect GemTalk Techincal Support to discuss.


Last updated: 4/3/18