- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: unable to debug coredump files
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2012 08:53 PM - last edited on тАО10-09-2012 11:19 PM by Maiko-I
тАО10-09-2012 08:53 PM - last edited on тАО10-09-2012 11:19 PM by Maiko-I
Hi,
i have tried to debug coredump file with "gdb" tool. but it is shown some below warnings.
kindly help on this.
sopdevb/corefiles> gdb /sopdev01/sop/sopdevb/v12.2.0/app/bin/porifb core.porifb.8195
HP gdb 6.1 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.
Copyright 1986 - 2009 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.1 (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.
..
Core was generated by `porifb'.
Program terminated with signal 11, Segmentation fault.
SEGV_MAPERR - Address not mapped to object
warning: Load module /sopdev01/sop/sopdevb/version_encours/../lib/libatk.so has been stripped.
Debugging information is not available.
warning: Load module /sopdev01/sop/sopdevb/version_encours/../lib/libutil.so has been stripped.
Debugging information is not available.
warning: Load module /logiciel/oracle/client_10204/lib/libclntsh.so.10.1 has been stripped.
Debugging information is not available.
warning: Load module /logiciel/oracle/client_10204/lib/libnnz10.so has been stripped.
Debugging information is not available.
#0 0xc000000000426140:0 in __doprnt_main+0xbe40 ()
from /usr/lib/hpux64/libc.so.1
P.S. This thread has been moved from HP-UX > Messaging to HP-UX > Languages and Scripting - HP Forums Moderator
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2012 09:18 PM
тАО10-09-2012 09:18 PM
Re: unable to debug coredump files
>but it is shown some below warnings.
Ignore them, go about your business.
The first command is to get a stack trace with: bt
>#0 0xc000000000426140:0 in __doprnt_main+0xbe40 /usr/lib/hpux64/libc.so.1
Looks like you are dying in libc's fprintf routine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2012 05:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2012 10:01 AM
тАО10-10-2012 10:01 AM
Re: unable to debug coredump files
(You might want to move the solution check from your post to mine, with the solution.
You can use the Post Options menu on the right.)