MPS issue job003782

TitleFALSE is not a safe default value for MPS_KEY_AMS_SUPPORT_AMBIGUOUS
Assigned userGareth Rees
DescriptionChristian Schafmeister reports [1] that he got the assertion:

poolams.c:1194: MPS ASSERTION FAILED: !(ams->shareAllocTable && amsseg->colourTablesInUse)
AnalysisThis assertion is caused, I believe, by the bug recorded in job000549 (blackening an AMS segment can break). But it shows another problem: the bug would never have been provoked if the AMS pool supported ambiguous references. But presumably Dr Schafmeister is accepting the default value for MPS_KEY_AMS_SUPPORT_AMBIGUOUS, which is FALSE.

It would be safer (fewer surprises) if the default value for this keyword argument were TRUE.
How foundcustomer
Evidence[1] <>
Created byGareth Rees
Created on2014-05-01 17:52:41
Last modified byGareth Rees
Last modified on2014-05-01 18:03:19
History2014-05-01 GDR Created.


Change Effect Date User Description
185927 closed 2014-05-01 18:02:53 Gareth Rees Default value for MPS_KEY_AMS_SUPPORT_AMBIGUOUS is now the safer value TRUE.