how to get more info from gdb trace

[lim255]

Hi All,

I am using GDB version:
Hewlett-Packard Wildebeest 1.0 (based on GDB 4.16)
(built for PA-RISC 1.1 or 2.0 (narrow), HP-UX 10.20)

My application is multithreaded. Everytime, my application
generates core due to some signals (SIGSEV, SIGILL or SIGABR),
GDB does not report the location which causes such signal to be
generated (I think).

Example trace:
(gdb) where
#0  0xc0138228 in _kill () from /usr/lib/libc.1
#1  0xc00a319c in _raise () from /usr/lib/libc.1
#2  0xc0083d08 in _abort () from /usr/lib/libc.1
#3  0xc14d69bc in ?? () from
/tcs/tools/Patches/osp/5.1/hpux1020/lib/libskel.sl
#4  0xc05a4d88 in cma__sig_deliver () from /usr/lib/libcma.1
#5  0xc05a5244 in cma___sig_sync_term () from /usr/lib/libcma.1
#6  <signal handler called>
#7  0x40f34c5c in ?? ()

Do you know how to make gdb to generate more information from line
#6 and #7?


thanks,
wlim


Sent via Deja.com
http://www.deja.com/