Gcc Compiled Application Cannot Be Debugged Using dbx (Doc ID 1006953.1)

Last updated on AUGUST 03, 2016

Applies to:

Oracle Solaris Studio - Version Forte Developer 6 Update 2 to 12.4 [Release 6.0 to 12]
All Platforms

Symptoms

An application compiled using gcc or g++ with the "-g" option can not be debugged using Oracle Solaris Studio dbx debugger because

Example messages

dbx: panic: "Symbol::ck_sclass_help"(): Assertion ((this->*ap)()) failed - "symbol.cc":3926

 

dbx: internal error: signal SIGSEGV (no mapping at the fault address)


Changes

The problem is expected to occur if gcc is configured to emit gcc stabs.
The problem is less likely to occur if gcc is configured to emit DWARF.

The problem is less likely to occur if a version of gcc or g++ is used against which dbx has been tested.
The problem is more likely to occur if the gcc or g++ version is newer than the most recent version against which dbx was tested.

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