gdb

[Gerald_13]

Hi,
I'd try to install gdb 6.2(last version)on hp 11.11 but with no success.
Is it possible to install gdb with hp 11.11 or it's a bad install of myself.
Thanks very much for your help.

regards,
Gerald (France)

[Robert-Jan Goossens · Accepted solution]

Hi Gerald,

There is a WDB version for 11i you can download it from below link.

http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,1665,00.html

Regards,
Robert-Jan

[H.Merijn Brand (procura]

My gcc ports include the latest gdb

My HP ITRC site pages can be found at (please use LA as primary choice):

USA Los Angeles http://mirrors.develooper.com/hpux/
SGP Singapore https://www.beepz.com/personal/merijn/
USA Chicago http://ww.hpux.ws/merijn/
NL Hoofddorp http://www.cmve.net/~merijn/

Enjoy, have FUN! H.Merijn

[Gerald_13]

OK thanks very much for your help.
So I find the version 5 of gdb but for HP 11.00 ?? My HP version is 11.11 (11i).
So, The install was succefull but now when I try to debbug I have a error message "Error while reading dynamic library list" (see down)
Thanks very much again!!
Regards,


[root] /opt/powercenter/6.2.1 #gdb -core=core pmcmd
HP gdb 5.0 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00
and target hppa1.1-hp-hpux11.00.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..(no debugging symbols found)...

warning: /opt/powercenter/6.2.1/core is truncated.

Proceeding anyway, but you may run into problems.
To avoid problems ensure that core file is not truncated.
Common reasons for truncation include system limit on core file size
and lack of disk space.


warning: core file may not match specified executable file.
Core was generated by `pmdtm'.
Program terminated with signal 6, Aborted.
Error while reading dynamic library list.

#0 0xc040c428 in ()

[Muthukumar_5]

Your corefile is not in a full format so that it can be debugged with gdb there. ulimit for corefile is not appropriate to have all core informations there.

Increase core file size as,

# Limit viewing
ulimit -Hc # Hard limit
ulimit -Sc # Soft limit

# Limit change to unlimited
ulimit -c unlimited

You can define hard limit, soft limit there with -Hc / -Sc

While executing core file you have to do with binary file which made that core file.

You can identify the binary file as,

# file core
# what core

IT will give the binary which caused core file creation there.

# GDB Debugging

gdb
gdb> bt

IT will give you back trace there. You can start to debug there.


HTH.