- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- HP linker dumps core, how to troubleshoot?
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
тАО03-20-2005 09:25 PM
тАО03-20-2005 09:25 PM
HP linker dumps core, how to troubleshoot?
How can I best troubleshoot this problem? The linker core file is not very helpful, at least no for gdb.
$ gdb /usr/ccs/lbin/ld32 core
GNU gdb 6.2
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "hppa2.0w-hp-hpux11.11"...(no debugging symbols found)...
Core was generated by `ld32'.
Program terminated with signal 10, Bus error.
warning: Couldn't read general-purpose registers from `.reg' section in core file.
Unable to find __dld_flags symbol in object file.
warning: Couldn't read general-purpose registers from `.reg' section in core file.
#0 0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x00000000 in ?? ()
Previous frame identical to this frame (corrupt stack?)
(gdb)
Any ideas?
-Harri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2005 09:32 PM
тАО03-20-2005 09:32 PM
Re: HP linker dumps core, how to troubleshoot?
strings core
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2005 10:29 AM
тАО03-24-2005 10:29 AM
Re: HP linker dumps core, how to troubleshoot?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2005 02:09 PM
тАО03-24-2005 02:09 PM
Re: HP linker dumps core, how to troubleshoot?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2005 04:55 PM
тАО03-27-2005 04:55 PM
Re: HP linker dumps core, how to troubleshoot?
--
ranga
[i work for hpe]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-28-2005 07:19 PM
тАО03-28-2005 07:19 PM
Re: HP linker dumps core, how to troubleshoot?
read(4, "f c _ M D 5 _ D i g e s t : : f ".., 304) .................................... = 304
Received signal 10, SIGBUS, in user mode, [SIG_DFL], partial siginfo
Siginfo: si_code: I_NONEXIST, faulting address: 0x530ff, si_errno: 0
PC: 0x1ee4f, instruction: 0x49370058
exit(10) [implicit] ................................................................... WIFSIGNALED(SIGBUS)|WCOREDUMP
My maxdsize and maxssize are:
maxdsiz 0XC0000000
maxssiz 0X800000
which I would think sufficient, but how to tell?
Btw. I have the same code compiling and linking ok on Solaris, Linux and Windows. Previous version was linking fine on HP-UX, the change has mainly been increased use of templates in C++ code, leading to a very big number of extremely long symbol names.
I guess I'll need to start looking into compiling all this in 64 bit mode, where the linker is GNU as well...