GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Core file
Operating System - HP-UX
1847491
Members
3748
Online
110265
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
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
Go to solution
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
10-18-2006 01:13 PM
10-18-2006 01:13 PM
Recently,in our Unix server(HP 9000) some core files frequently appear.To core files,I have four questions.would you please answer them?
1.what is core files?
2.What is the root cause that they bring out?
3.how to treat with it when they occured?
4.By which tools,can we analyse it?
Thanks for your help.
1.what is core files?
2.What is the root cause that they bring out?
3.how to treat with it when they occured?
4.By which tools,can we analyse it?
Thanks for your help.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2006 01:22 PM
10-18-2006 01:22 PM
Re: Core file
try with "file core" to see what type of core file is it? How big is it? If it is OS generated then use "strings core" and may give some information. If it is application generated core file then you need to look at application debugging methods.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2006 01:35 PM
10-18-2006 01:35 PM
Re: Core file
Thanks for you assistance.
If only by core files can we get the result?If we had remove it,what will we do?
If there are some debugging tools to analyse it?
If only by core files can we get the result?If we had remove it,what will we do?
If there are some debugging tools to analyse it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2006 01:41 PM
10-18-2006 01:41 PM
Solution
1) It is a dump of a process memory image plus some additional data.
2) The root cause could be something as simple as a signal (kill) sent to the process, a memory violation because, for example, the process's stack exceeded the maxssiz kernel parameter but more than likely the cause is a programming error.
3) Fix the underlying problem which generally means a programming change.
4) You first run the file command against the core file and it will identify the executable. Next, you run a debugger against the core file and get a stack trace. Analyzing a stack trace is difficult without the source code. In general, if you have to ask this question then you aren't the one to analyze or fix the problem.
2) The root cause could be something as simple as a signal (kill) sent to the process, a memory violation because, for example, the process's stack exceeded the maxssiz kernel parameter but more than likely the cause is a programming error.
3) Fix the underlying problem which generally means a programming change.
4) You first run the file command against the core file and it will identify the executable. Next, you run a debugger against the core file and get a stack trace. Analyzing a stack trace is difficult without the source code. In general, if you have to ask this question then you aren't the one to analyze or fix the problem.
If it ain't broke, I can fix that.
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 2026 Hewlett Packard Enterprise Development LP