My Oracle Support Banner

Backtracing NCC and 3C Core Files with gdb No Longer Returns a Valid Stacktrace (Doc ID 2464622.1)

Last updated on AUGUST 19, 2020

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 6.0.0 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) versions 6.0.0.0 and above, there is an issue when using the GNU Debugger (gdb) with any core files left by a crashed process to try and backtrace the core file.

Attempting to backtrace a core file fails and returns no useful information.  For example:

As a result, it is not possible to determine the code path which lead to the crash.

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.