Sponsored Content
Full Discussion: identifying core dump files.
Top Forums UNIX for Dummies Questions & Answers identifying core dump files. Post 302420283 by methyl on Tuesday 11th of May 2010 07:48:11 AM
Old 05-11-2010
The "file" test suggested above is very important when dealing with program core dump files, directories called "core*", or files called "core*".
Some systems dump core with a filename core.<pid> where <pid> is the process ID.

Beware that the file containing the text for "man core" is usually called "core.4". Well worth seraching your system to see what variety of filenames you have.

I have seen systems destroyed by deleting the unix "core" package when blindly trying to delete program core dumps.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies

2. UNIX for Dummies Questions & Answers

core dump

does any one have read a core dump? is there any reader for that? or may i know what is the use of that core which takes sometimes memory in GBs? :) (6 Replies)
Discussion started by: sskb
6 Replies

3. UNIX for Dummies Questions & Answers

core dump

Hi , Working on AIX 4.3. An internal error from my apps engine suddenly causes the engine to die. During this time i do notice a core file being dumped in the directory from where I try to re-start my engine. Q is how does one read this core file, or I should say 'what is this core file'? thnx (2 Replies)
Discussion started by: buRst
2 Replies

4. UNIX for Dummies Questions & Answers

core dump

I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start but savecore failed to create the two files, that is vmcore.n and vmunix.n. savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname 1)... (4 Replies)
Discussion started by: hassan2
4 Replies

5. Programming

about core dump

MY friends: my program under sco unix have a problem? it create a core dump file on the path when execute program , but i can't find the error of the C program ,i don't know how to see the error about my program use core, please help me or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies

6. UNIX for Advanced & Expert Users

core dump

Hi All, i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know. sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies

7. Red Hat

Process does not dump any core files when crashed even if coredumpsize is unlimited

Hello Im using redhat and try to debug my application , its crashes and in strace I also see it has problems , but I can't see any core dump I configured all the limit ( im using .cshrc ) and it looks like this : cputime unlimited filesize unlimited datasize unlimited... (8 Replies)
Discussion started by: umen
8 Replies

8. UNIX for Dummies Questions & Answers

No core dump

my progrme complaints 'Segmentation fault'. How to let it print 'Segmentation fault(core dumped)' and generate core dump file? $ulimit unlimited (22 Replies)
Discussion started by: vistastar
22 Replies

9. AIX

Identifying Underlying Physical Core Count - AIX

Hi guys, I was wondering if you could help me out with a query I had. Is there a query to identify the total processor core count of the physical AIX box from which I am running 4 LPARs. I have run the lscfg, lparstat-i and lsdev -Cc processor commands however they just show me the cores... (9 Replies)
Discussion started by: OsmosisJones
9 Replies
gcore(1)							   User Commands							  gcore(1)

NAME
gcore - get core images of running processes SYNOPSIS
gcore [-pgF] [-o filename] [-c content] process-id... DESCRIPTION
The gcore utility creates a core image of each specified process. By default, the name of the core image file for the process whose process ID is process-id will be core.process-id. OPTIONS
The following options are supported: -c content Produces core image files with the specified content. The content description uses the same tokens as in coreadm(1M). The -c option does not apply to cores produced due to the -p or -g flags. -F Force. Grabs the target process even if another process has control. -g Produces core image files in the global core file repository with the global content as configured by coreadm(1M). The com- mand will fail if the user does not have permissions to the global core file repository. -o filename Substitutes filename in place of core as the first part of the name of the core image files. filename can contain the same tokens to be expanded as the paths in coreadm(1M). -p Produces a core image file in the process-specific location with the process-specific content for each process as config- ured by coreadm(1M). The command will fail if the user does not have permissions to the per-process core file repository. OPERANDS
The following operand is supported: process-id process ID EXIT STATUS
The following exit values are returned: 0 On success. non-zero On failure, such as non-existent process ID. FILES
core.process-id core images ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWtoo | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ Command Syntax is Evolving. Output Format(s) are Unstable. SEE ALSO
kill(1), coreadm(1M), setrlimit(2), core(4), proc(4), attributes(5) NOTES
gcore is unaffected by the setrlimit(2) system call using the RLIMIT_CORE value. SunOS 5.10 11 Feb 2004 gcore(1)
All times are GMT -4. The time now is 04:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy