08-26-2011
Quote:
Originally Posted by
donadarsh
use string command to read all string from core and redirect it to some tmp file.
This is not the proper way to debug a core file. use a debugger like already suggested.
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 OPENSOLARIS
gcore
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 is 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 fails 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 configured
by coreadm(1M). The command fails if the user does not have permissions to the per-process core file repository.
OPERANDS
The following operand is supported:
process-id process ID
USAGE
Caution should be exercised when using the -F flag. Imposing two controlling processes on one victim process can lead to chaos. Safety is
assured only if the primary controlling process, typically a debugger, has stopped the victim process and the primary controlling process
is doing nothing at the moment of application of the proc tool in question.
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. |
+-----------------------------+-----------------------------+
The command syntax is Evolving. The Output Formats 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.11 19 Jun 2006 gcore(1)