1834913 Members
3195 Online
110071 Solutions
New Discussion

Re: GDB debugger

 
jpcast_real
Regular Advisor

GDB debugger

Hello ,

we are using the debugger to analize the core generated by an application . The problem appears when we try to analize the stack trace of the core . This is the error which wdb gives us:
warning: GDB cannot print complete stack trace since some shared libraries are missing. Set GDB_SHLIB_PATH and try again.
Invalid
#1 0xc003b834 in ()
#2 0xc003b834 in ()
#3 0xc003b834 in ()
#4 0xc003b834 in ()
Cannot access memory at address 0xffffffe9


This are the environment variables I have set in my system:

SHLIB_PATH=/usr/bin
SDB_SHLIBPATH=/usr/bin
GDB_SHLIB_PATH=/usr/lib
SDB_SHLIB_PATH=/usr/bin

My operating system data and debugger release:


501:Porthos:/mad501/output/cores>swlist -l fileset | grep -i wdb
# WDB B.11.11.13-01 HP Wildebeest (HP WDB) Debugger
WDB.WDB B.11.11.13-01 HP Wildebeest (HP WDB) Debugger
WDB.WDB-DOC B.11.11.13-01 HP Wildebeest (HP WDB) Documentation
WDB.WDB-MAN B.11.11.13-01 HP Wildebeest (HP WDB) Man Pages
# WDB-GUI B.11.11.13-01 GUI for the HP WDB Debugger
WDB-GUI.WDB-GUI-HELP B.11.11.13-01 GUI online help for the WDB Debugger
WDB-GUI.WDB-GUI-MAN B.11.11.13-01 GUI man pages for the WDB Debugger
WDB-GUI.WDB-GUI-RUN B.11.11.13-01 GUI runtime components for the WDB Debugger
501:Porthos:/mad501/output/cores>swlist -l fileset | grep -i gdb
# gdb 5.3 gdb
gdb.gdb-RUN
501:Porthos:/mad501/output/cores>model
9000/800/L3000-7x

Un saludo y gracias





-----Mensaje original-----
De: Diaz, Roberto [mailto:roberto.diaz.gavilanes@hp.com]
Enviado el: jueves, 29 de septiembre de 2005 13:14
Para: Perez Castillo, Javier
Asunto: Caso 1208887651



Hola Javier,

Puedes indicarme cuál es el problema?

Saludos,

Roberto.

Here rests one who was not what he wanted and didn't want what he was
1 REPLY 1
Stephen Keane
Honored Contributor

Re: GDB debugger

In gdb there is a command

> sharedlibrary libABC.sl

where you can load the shared libraries individually.