Sponsored Content
Top Forums UNIX for Dummies Questions & Answers help, what is the difference between core dump and panic dump? Post 2934 by Neo on Monday 11th of June 2001 08:08:59 PM
Old 06-11-2001
Any UNIX process can 'core dump', however only the kernel process 'panics'.
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. UNIX for Dummies Questions & Answers

Core dump in HP-UX..

Hi All I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies

4. UNIX for Advanced & Expert Users

Core Dump

Hello all, Iam new to unix while executing java program which finely working in windows know iam testing with unix ,but in unix while executing iam getting core dump, my application is in client server environment and it is menu drivrn application on clicking options no problem but after some time... (1 Reply)
Discussion started by: vinp
1 Replies

5. AIX

core dump

My application gives core dump. When i am debugging with dbx getting instructions below: pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error) pthreaded.c, 1941: PTHDB_INTERNAL (internal error) Illegal instruction (illegal opcode) in . at 0x0 warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies

6. AIX

Disabling saving of system dump while kernel panic

Hi, Is there an option to disable saving of system dump when a user invokes a kernel panic using sysdumpstart command. Also, is there any other way of invoking a kernel panic other than using sysdumpstart? Thanks, Kanna (3 Replies)
Discussion started by: kanna_geekworkz
3 Replies

7. AIX

Core dump

Hi , I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information. ux201p3:e46123> dbx capsWrkstnMgr core Type 'help' for help. reading symbolic information ... Segmentation fault in malloc_common.extend_brk at... (1 Reply)
Discussion started by: rps
1 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. HP-UX

Core dump in HP-UX

Hi Guys, I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself. Thanks Messi (1 Reply)
Discussion started by: messi777
1 Replies

10. Solaris

core dump

Hi guys, just want to know which core file pattern is best to set for core dumps: 1) per-process file name pattern or 2) global file name pattern. I will really appreciate an explanation why the chosen one is better. Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 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 01:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy