04-23-2003
The consensus was to use either adb or gdb. Adb is a debugger (sort of cryptic man page as well) that will allow you to look at a core. Gdb is the open source version of adb. It was also suggested that you use either command (adb or gdb) on the machine that the core was created on. Also you can use 'strings core > foo.log' and look at some general info.
10 More Discussions You Might Find Interesting
1. Solaris
I have the following set up on a Sun server running solaris 5.8 for core dump generation
coreadm
global core file pattern: /var/core
init core file pattern: /var/core
global core dumps: enabled
per-process core dumps: enabled
global setid core dumps:... (4 Replies)
Discussion started by: handak9
4 Replies
2. Programming
hi everyone,
Right now when I do:
strcmp(s1, s2);
i get a core dump because at times s1 or s2 can be nothing so that makes strcmp() core dump.
What is the solution, if at times I expect one of them (or both) to be NULL?
I want to be able to compare that s1 is NULL and s2 is "blah" or... (6 Replies)
Discussion started by: annie
6 Replies
3. SCO
Anyone know how you go about interrogating a panic / core dump with crash for SCO Unix (5 Replies)
Discussion started by: ccarcher
5 Replies
4. UNIX for Advanced & Expert Users
Hi,
Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)
Discussion started by: nsdeeps
2 Replies
5. Programming
My program is not dumping core when hitting a segmentation violation inside a thread.
However, it dumps core when the segv occurs within main.
Any ideas on how to diagnose this?
AIX 5.3 (4 Replies)
Discussion started by: bean66
4 Replies
6. Solaris
i had a situation where a process was defunct. preap would not reap the process and gcore would not work properly (not sure why). therefore, the suggestion was to force a panic and collect the core dump. obviously you could do a savecore -L and capture the dump without bringing down the system.... (3 Replies)
Discussion started by: pupp
3 Replies
7. Ubuntu
Hello,
I am debugging a program which works as daemon. It sigfaults, unfortunately I'm unable to generate core dump file. Here is what I am doing:
tsurko@bastila:~$ ulimit -c unlimited
tsurko@bastila:~$ ulimit -c
unlimited
tsurko@bastila:~$ cat /etc/sysctl.conf | grep 'core_pattern'... (1 Reply)
Discussion started by: tsurko
1 Replies
8. Red Hat
Hi
I have a Fedora installed and I try to generate my application's core dump file.
My system has no coredump limit:
$ ulimit
core file size (blocks, -c) unlimited
But when my application crashes no core dumps generated. I can generate dump file using gcore but it is not appropraite... (1 Reply)
Discussion started by: xyzt
1 Replies
9. Programming
I'm working on a program in Linux with a group of people scattered around the country. When we have a crash, I like to send a core dump to the appropriate person so that they can understand the problem better. The problem is that our application uses several gigabytes worth of data and these... (4 Replies)
Discussion started by: bmsterner
4 Replies
10. HP-UX
kill -SEGV <pid> gives me the core file for that process but also terminates the process.
Can I not get the core dump without terminating the process ? (2 Replies)
Discussion started by: mohtashims
2 Replies
gcore(1) General Commands Manual gcore(1)
NAME
gcore - get core images of running processes
SYNOPSIS
filename] process-id...
DESCRIPTION
The command creates a core image of each specified process. By default, the name of the core image file for process-id will be The process
information in the core file can be obtained by using debuggers.
When the command creates a core image of each specified process, the process is temporarily stopped. Further, when the creation of core
image is complete, the process continues to execute.
Options
Creates the core file with name of the file as
If multiple process-id values are specified, filename will be common for all the core image files. See the section.
Operands
process-id The process ID for which a core image file will be created.
RETURN VALUE
Upon completion, exits with one of the following values:
A core file was successfully created.
An error condition was encountered.
In such a case, the creation of a core file is not guaranteed. The error conditions could be because of
o A nonexistent or incorrect process ID was specified.
o An invalid option was specified.
o The current working directory of the process or directory from which was invoked had no write permissions.
o The current working directory of the process was not accessible.
o The file system is full.
EXAMPLES
Example 1
Dump the core image of process 1030 in the file "core.1030".
Example 2
Dump the core image of the process 1030 in the file "test.1030".
Example 3
Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files "core.1030", "core.1031", "core.1032", "core.1033".
Example 4
Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files
FILES
Core image file for process-id. (Both where is invoked and the current working directory of the process.)
AUTHOR
was developed by Chris Bertin (HP).
SEE ALSO
adb(1), gdb(1), kill(1), ttrace(2), a.out(4), core(4).
gcore(1)