CM Signal 11 On Calling PIN_ERR_LOG_MSG Macro With NULL
Last updated on NOVEMBER 21, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Solaris platform :
Upon calling the PIN_ERR_LOG_MSG macro on value which in some scenarios has null values, signal 11 is thrown.
One would expect that CM should not throw Signal 11 in this way.
Error snippet in cm pinlog :
Steps to reproduce :
1. Call PIN_ERR_LOG_MSG macro in any customized policy opcode, as follows :
// Demonstrate that PIN_ERR_LOG_MSG() causes issue when passed NULL parameter
PIN_ERR_LOG_MSG(PIN_ERR_LEVEL_DEBUG,"fm_bill_pol_event_search_custom_custom before passing NULL");
PIN_ERR_LOG_MSG(PIN_ERR_LEVEL_DEBUG,"fm_bill_pol_event_search_custom_custom after passing NULL");
2. execute the custom policy opcode
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms