cancel
Showing results for 
Search instead for 
Did you mean: 

Memory Core dump

 
Johnson Punniyalingam
Honored Contributor

Memory Core dump

[abc@abcabc15] [ABCSSUA] /project/abc/bin > ls -lrt *part*
-rwxr--r--   1 abc        abc         171536 Jan 21 16:00 ld_part_struct
[abc@abcabc15] [ABCSSUA] /project/abc/bin > gdb ld_part_struct /tmp/ABC_core/core_ld_part_struct
HP gdb 6.3 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.
Copyright 1986 - 2011 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.3 (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.
..
warning: Load module /project/abc/bin/ld_part_struct has been stripped.
Debugging information is not available.

(no debugging symbols found)...
Core was generated by `ld_part_struct'.

warning: ld_part_struct is 14 characters in length.  Due to a limitation
        in the HP-UX kernel, core files contain only the first 14 characters
        of an executable's name.  Check if ld_part_struct is a truncated name.
        If it is so, core-file, packcore and other commands dealing with
        core files will exhibit incorrect behavior.  To avoid this, issue
        exec-file and symbol-file commands with the full name of the executable
        that produced the core; then issue the core-file, packcore or other
        core file command of interest.

Program terminated with signal 11, Segmentation fault.
SEGV_MAPERR - Address not mapped to object
(no debugging symbols found)...#0  0xc000000000211ab0:0 in _lwp_kill+0x30 ()
   from /usr/lib/hpux64/libpthread.so.1
(gdb) exit

Problems are common to all, but attitude makes the difference
1 REPLY 1
Dennis Handly
Acclaimed Contributor

Re: Memory Core dump

>warning: Load module ld_part_struct has been stripped.

 

If it is stripped, not much we can do to help.

Can you get a full stack trace with "bt".

 

>#0  0xc000000000211ab0:0 in _lwp_kill+0x30

 

This indicates the process killed itself.  Probably after it caught signal 11 in a signal handler.