Debugging Core Files Using HP WDB (5900-1573; WDB 6.2; January 2011)

However, the shared memory segments can be dumped into the core file if you set
the following kernel symbols:
• core_addshmem_read
This kernel symbol controls if shared memory segments that are mapped read-only
into a process are dumped in a core file. To view the current value of the tunable
and change it , enter the following commands:
# echo 'core_addshmem_read/X'|adb -k /stand/vmunix /dev/kmem
core_addpid:
core_addpid: 0
# echo 'core_addshmem_read/W 1'|adb -k -w /stand/vmunix /dev/kmem
core_addpid: 0 = 1
• core_addshmem_write
This kernel symbol controls if shared memory segments that are mapped
read/write into a process are dumped in a core file. To view the current value
of the tunable and change it , enter the following commands:
# echo 'core_addshmem_write/X'|adb -k /stand/vmunix /dev/kmem
core_addpid:
core_addpid: 0
# echo 'core_addshmem_write/W 1'|adb -k -w /stand/vmunix /dev/kmem
core_addpid: 0 = 1
NOTE:
• HP does not provide complete support for these kernel symbols.
• The large size of the shared memory segments must be taken into account before
using these kernel symbols.
2 How do I check if the system is enabled for creating core files with sizes greater than
2 GB? How do I enable the system for creating core files with sizes greater than 2
GB?
To check if the system is enabled for creating core files with sizes greater than 2 GB,
enter the following command:
fsadm <filesystem>
If this command displays “largefiles”, the system is enabled for creating core files
greater than 2 GB.
To enable a system for creating core files greater than 2 GB, enter the following
command:
fsadm -o largefiles <filesystem>
3 How do I verify if a core file is truncated?
To verify if a core file is truncated, enter the following command:
elfdump -o -S core
58