Backtracing NCC Corefiles with GDB Fails with "warning: Wrong size gregset in core file" or "warning: Wrong size fpregset in core file" (Doc ID 2056965.1)

Last updated on SEPTEMBER 22, 2015

Applies to:

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

Symptoms

When attempting to obtain a backtrace from core file left behind by an Oracle Communications Network Charging and Control (NCC) application, GDB (GNU Debugger) throws the following errors on startup:

warning: Wrong size gregset in core file.

warning: Wrong size fpregset in core file.

Full context:

root@SLC# gdb /IN/service_packages/E2BE/bin/BeClient core-SLC-19360-BeClient

GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.11"...
Reading symbols from /IN/service_packages/E2BE/lib/libbeEventFactory.so...done.
...
Reading symbols from /lib/ld.so.1...done.
Loaded symbols for /lib/ld.so.1

warning: Wrong size gregset in core file.

warning: Wrong size fpregset in core file.
Core was generated by `/IN/service_packages/E2BE/bin/BeClient'.
Program terminated with signal 4, Illegal instruction.
[New process 84896    ]

warning: Wrong size gregset in core file.

warning: Wrong size fpregset in core file.
#0  0x00000000 in ?? ()

Due to this, attempts to run the backtrace (bt) command also fail:

(gdb) bt
#0  0x00000000 in ?? ()

(gdb) bt full
#0  0x00000000 in ?? ()

Cause

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