My Oracle Support Banner

CM Signal 11 on Calling PIN_ERR_LOG_MSG Macro with NULL (Doc ID 2296449.1)

Last updated on NOVEMBER 01, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

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
    {
    char *null_str=NULL;
    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,null_str);
    PIN_ERR_LOG_MSG(PIN_ERR_LEVEL_DEBUG,"fm_bill_pol_event_search_custom_custom after passing NULL");
    }
  2. execute the custom policy opcode

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.