HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: coredump
Operating System - HP-UX
1834142
Members
2328
Online
110064
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-08-2010 09:28 PM
07-08-2010 09:28 PM
coredump
Hi,
What is this coredump?How can I check it and how to clear it??
What is this coredump?How can I check it and how to clear it??
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2010 09:37 PM
07-08-2010 09:37 PM
Re: coredump
hi,
check this docu :
"Generating and Retrieving System Core Dumps"
http://docs.hp.com/en/J2237-90005/ch06s05.html
the crash dump can be generated if the system crash ( HW or SW failure ) or if you make TOC.
mikap
check this docu :
"Generating and Retrieving System Core Dumps"
http://docs.hp.com/en/J2237-90005/ch06s05.html
the crash dump can be generated if the system crash ( HW or SW failure ) or if you make TOC.
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2010 10:59 PM
07-08-2010 10:59 PM
Re: coredump
Michal referred to an old manual (from 1995). Since then, the terminology has changed a little.
- Core dump:
This happens most often when an application has a programming bug and tries to access a memory location it's not allowed to access. At that point, the Memory Management Unit in the processor stops the program and the OS will display an error message, like "Segmentation Fault".
If the ulimit value "coredumpsize" ("ulimit -c" command) is not set to 0, the application's memory space will be copied to a file named "core" in the current directory, and the text "(core dumped)" is added to the error message. This file will allow a programmer to find out exactly what the application was doing when the error occurred.
- Crash dump:
This used to be called "system core dump", as in Michal's document. But too often it was confused with the regular core dumps, so the name was changed. The proper name is now "crash dump". Please don't confuse ordinary core dumps with crash dumps: they are very different.
A crash dump happens when you press the TOC button on the server, or use the TC command in the GSP/MP, or if there is a serious problem at the kernel level (a bug in a driver, memory corruption that cannot be fixed by ECC, etc.).
In this situation, the system firmware takes control, and writes the contents of the system memory to a configured dump area (by default, it's the primary swap /dev/vg00/lvol2). Then the system reboots, and before activating any swap areas, the start-up scripts will copy and compress the dump into files in /var/adm/crash.
HP Support can give you a special "crashinfo" program for making a quick analysis of a crash dump. But if you send the crash dump to HP Support, they can analyze it in more detail.
MK
- Core dump:
This happens most often when an application has a programming bug and tries to access a memory location it's not allowed to access. At that point, the Memory Management Unit in the processor stops the program and the OS will display an error message, like "Segmentation Fault".
If the ulimit value "coredumpsize" ("ulimit -c" command) is not set to 0, the application's memory space will be copied to a file named "core" in the current directory, and the text "(core dumped)" is added to the error message. This file will allow a programmer to find out exactly what the application was doing when the error occurred.
- Crash dump:
This used to be called "system core dump", as in Michal's document. But too often it was confused with the regular core dumps, so the name was changed. The proper name is now "crash dump". Please don't confuse ordinary core dumps with crash dumps: they are very different.
A crash dump happens when you press the TOC button on the server, or use the TC command in the GSP/MP, or if there is a serious problem at the kernel level (a bug in a driver, memory corruption that cannot be fixed by ECC, etc.).
In this situation, the system firmware takes control, and writes the contents of the system memory to a configured dump area (by default, it's the primary swap /dev/vg00/lvol2). Then the system reboots, and before activating any swap areas, the start-up scripts will copy and compress the dump into files in /var/adm/crash.
HP Support can give you a special "crashinfo" program for making a quick analysis of a crash dump. But if you send the crash dump to HP Support, they can analyze it in more detail.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP