Sponsored Content
Full Discussion: No core dump
Top Forums UNIX for Dummies Questions & Answers No core dump Post 302479976 by DGPickett on Monday 13th of December 2010 02:27:37 PM
Old 12-13-2010
I used to run a cron script to find core files, generate reports on them (stack trace if possible, ownership or file output at least), save them in /tmp compressed (in case they are important and might get overwritten), and email the report to the dev group. People write a lot of unattended scripts with loose error checking, and a core report may raise awareness of a hole in the code or why a periodic process has no effect. So, search everywhere for a file called core, run it through ls -l and file, and see what has been dying! Also, do not run code in unwritable directories if you want a core.

The cd is much overused in the popular UNIX pragma. There are lots of ways to handle paths without $PWD, like X cut/paste and command recall. It makes shell command history less useful! Life is simpler if you stay home most of the time!
 

10 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

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

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

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

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

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

7. Programming

core dump

how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies

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

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
crashutil(1M)															     crashutil(1M)

NAME
crashutil - manipulate crash dump data SYNOPSIS
version] source [destination] DESCRIPTION
copies and preserves crash dump data, and performs format conversions on it. Common uses of include: o Copying portions of a dump that still reside on a raw dump device into a crash dump directory. o Converting between different formats of crash dumps. o Copying crash dumps from one directory, or medium, to another. will write to its destination the crash dump it reads from its source. The crash dump format used to write the destination is specified with if is not specified, the destination will have the same format as the source. If no destination is specified, source is used; the format conversion will be done in place in the source, without copying. When completes successfully, the entire contents of the crash dump will exist at destination; any portions that had still been on raw dump devices will have been copied to destination. There are three known dump formats: (Version 0) This format, used up through HP-UX 10.01, consists of a single file containing the physical memory image, with a 1-to-1 cor- respondence between file offset and memory address. Normally there is an associated file containing the kernel image. sources or destinations of this type must be specified as two pathnames to plain files, separated by whitespace; the first is the core image file and the second is the kernel image file. (Version 1) This format, used in HP-UX 10.10, 10.20, and 10.30, consists of a directory containing an file, the kernel file, and numerous files, which contain portions of the physical memory image. sources or destinations of this type should be specified as the pathname to a core directory. (Version 2) This format, used in HP-UX 11.00 and later, consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which were not. sources or destinations of this type should be specified as the pathname to a crash directory. (Version 3) This format is used in HP-UX Release 11i Version 1.0 and later. It is very similar in structure to the format in that it consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which were not. In addition to the primary file, there are auxiliary index files, that contain metadata describing the image files containing the memory pages. This format will be used when the dump is compressed. See crashconf(1M). Other formats, for example tape archival formats, may be added in the future. When the source and destination are different types of files -- for example, when source is a directory and destination is a pair of plain files -- both must be specified. Options (Quiet) Disables the printing of progress messages. Warning and error messages are still printed. Specifies the version of the destination format. Allowed values are 0, 1, 2 or 3. Also allowed is the keyword which specifies that the destination format should be the same as the current source format. is the default if is not specified. If the destination format is then the source format should also be Conversion to from older formats is not supported. RETURN VALUE
Upon exit, returns the following values: 0 The operation was successful. 1 The operation failed, and an appropriate error message was printed. EXAMPLES
An HP-UX 11.00 crash dump was saved by savecrash(1M) to The flag was specified to savecrash, specifying that only those portions of the dump which were endangered by swap activity should be saved; the rest are still resident in the raw dump devices. To save the remainder of the dump into the crash dump directory, use: If preferred, the completed crash dump directory could be in a different location -- perhaps on another machine via NFS: To debug this crash dump using tools which do not understand the most current crash dump format, convert it to the older core directory format: or the even older "core file and kernel" format: AUTHOR
was developed by HP. SEE ALSO
savecrash(1M), crashconf(1M). crashutil(1M)
All times are GMT -4. The time now is 01:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy