|
|
Sponsored Content
Homework and Emergencies
Emergency UNIX and Linux Support
How to open the core dump file in linux?
Post 302549458 by vanitham on Tuesday 23rd of August 2011 06:03:08 AM
08-23-2011
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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. UNIX for Dummies Questions & Answers
Hi All,
is there any way to find out the optimal/would be size of the cor dump file generated by the system while a process got terminated abnormally?
Basically we have been asked to provide the size of the core dump file being generated by the administrators who maintained the UNIX boxes.... (4 Replies)
Discussion started by: pushp.gahlot
4 Replies
4. Programming
by what name does a core dump file stored???
like i wrote a test code:
//dump.c
main()
{
char *p=NULL;
printf("%s",p);
}
of course the above code will produce a segmentation fault. but i cant see any file named core in my CWD. am using SUN0S 5.9 (6 Replies)
Discussion started by: vikashtulsiyan
6 Replies
5. Programming
Hi All,
May be it is a stupid question, but, I would like to know what is the advantage using a core dump file at the moment of debugging using gdb.
I know a core dump has information about the state of the application when it crashed, but, what is the difference between debugging using the... (2 Replies)
Discussion started by: lagigliaivan
2 Replies
6. Shell Programming and Scripting
Segmentation fault(core dumped)
but I cant find core file any where. how to make it out?
I try the command:ulimit -c unlimited, I even added it to the .bashrc file.And I removed ulimit setting in /etc/init.d/function. And there's no ulimit setting in /etc/profile. And I tried sudo find /... (8 Replies)
Discussion started by: vistastar
8 Replies
7. Linux
How do i get pointer to thread's local storage or thread specific data while analyzing core dump for linux ?
i use pthread_setspecific to store some data in the pthread's local stoare.
my multi threaded program on linux crashed, and i want to see what is stored in current running thread's... (2 Replies)
Discussion started by: vishwasungal
2 Replies
8. Solaris
I am new to UNIX.
My Application is using c (.so files) and Java code.
My application crashes and CORE DUMP file is generated ,which is huge.
Now I want to view the CORE DUMP file to debug the application using dbx without starting process again.
By only using the CORE DUMP file and dbx ,can i... (1 Reply)
Discussion started by: satde
1 Replies
9. UNIX for Dummies Questions & Answers
Can any body provide me some good link to learn to create and analyze linux user mode application / kernel module core dumps? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
10. Red Hat
Hello All,
I am new joiner of this forum.I am new to Linux shell scripting.
At present I have identified 1 application which stalls very frequently (PID is say xyz) and I am not having much information in its application log to identify the root cause of stalling. I need to take the core dump... (19 Replies)
Discussion started by: Anjan Ganguly
19 Replies
LEARN ABOUT HPUX
cr_open
cr_open(3) Library Functions Manual cr_open(3) NAME
cr_open() - open crash dump for reading SYNOPSIS
DESCRIPTION
The library call opens a crash dump and passes back a crash dump descriptor. The path argument points to a path name naming a crash dump directory or file, and must not exceed bytes in length. The CRASH * to which crash_cb points is set to a crash dump descriptor, which can then be passed to the other functions to access the crash dump. flags is a bitmask of zero or more of the following flag values, which affect the operation of future calls to libcrash routines for this crash dump, except for cr_verify(3), which has its own flags parameter. The library will not attempt to verify checksums of files in the crash dump if this flag is set. The library will write messages to stderr during time-consuming operations (decompressions and checksums) if this flag is set. RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5). EXAMPLES
The following call to opens crash dump contained in the directory and returns the crash dump descriptor For an example of reading the crash dump see the cr_read(3) manual entry. AUTHOR
was developed by HP. SEE ALSO
cr_close(3), cr_perror(3), libcrash(5). cr_open(3)