backtrace/2255: gdb - backtrace fails on solaris 10

reglera@msg.de reglera@msg.de
Fri Apr 20 07:58:00 GMT 2007


>Number:         2255
>Category:       backtrace
>Synopsis:       gdb - backtrace fails on solaris 10
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 20 08:58:01 BST 2007
>Closed-Date:
>Last-Modified:
>Originator:     reglera@msg.de
>Release:        gdb 6.5 / 6.6
>Organization:
>Environment:
Solaris 10 (5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Fire-880)
>Description:
Hello !

I have problems in getting a backtrace of a dumped core using gdb on solaris 10. Here's the output:

Core was generated by `abc'.
#0  0x00000000 in ?? ()
#0  0x00000000 in ?? ()
No symbol table info available.

The application 'abc' is a 'hello-world'-programm compiled by a Sun-Workshop-compiler using the g-option for including debugging information. The output using dbx looks fine:

Reading abc
core file header read successfully
Reading ld.so.1
Reading libc.so.1
Reading libc_psr.so.1
program terminated by signal 0 (UNKNOWN SIGNAL)
=>[1] _write(0x1, 0xff3704f8, 0xc, 0xff36c308, 0x10, 0xff36c340), at 0xff3415c0
  [2] _xflsbuf(0xff36c7cc, 0x42, 0xff370504, 0x6c72640a, 0xff00, 0x0), at 0xff324adc
  [3] _ndoprnt(0xff36c7cc, 0x42, 0xfffffff4, 0xc, 0xff370504, 0xfffffff4), at 0xff31764c
  [4] printf(0x106a0, 0xff36c7bc, 0x0, 0xff36c7da, 0xff368284, 0xc), at 0xff3183fc
  [5] main(0x1, 0xffbff3b4, 0xffbff3bc, 0x20838, 0xff3a00c0, 0xff3a0100), at 0x105e0


Any hints?

Regards, Alex.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the Gdb-prs mailing list