In sun solaris whenever a jvm crashes we used to get the core file generated in binary format. We convert this core file to human readable format using
How can we convert the core file generated in HPUX to human readable format ? We dont have pstack either.
ok heres a question, :confused: well obviously
i have here my old old motorola system V/88
in my /usr/adm folder i have a file called kernelcore which is 16mb (the computer has 16mb ram too), we believe this is the contents of our ram when the system crashed back in feb last year!
Is it save... (2 Replies)
please help me, what can i do with the bountiful amount of core files our systems seem to have on occassional basis?? how do I analyze it and determine why the core file was dumped by the application that dumped it. the operating systems we use are solaris, DG-UX and linux red hat systems. (5 Replies)
Solaris v5.6
What log files should be checked out as part of your sys admin daily routine?
I've printed out my syslog.conf file, and looked in /var/log and found authlog, syslog, and POPlog. I know of /var/adm/messages.
What others should I be looking for?
I know of the "find" command. I... (8 Replies)
Does anyone know any tools or how to really get something out of a core file.
I can use strings and look for certain things like out of memory.
I am trying to use adb but I can't make heads or tails from it. I guess it is my lack of know how with the adb/mdb debugger.
anything would... (3 Replies)
I have a SUN Ultra 80 running Solaris 5.8 I have a couple of applications running on it. The /var/core file seems to be filling up by 2% per day.
Could anyone pls suggest how to read contents of /var/core I have read couple of docs but seems to be too cumbersome. Please suggest something
example... (3 Replies)
Hi,
We have an application ASPA . The application related processes are running in /ASPA/bin directory . now whenever a process terminates abruptly , a core file should be generated (correct me if i am wrong) in the
/ASPA/bin directory . But i am not able to see any such files . The... (4 Replies)
Hi the following c-code utilizing the 'read()' man 2 read method cant read in files larger that 2gig.
Hi I've found a strange problem on ubuntu64bit, that limits the data you are allowed to allocate on a 64bit platform using the c function 'read()'
The following program wont allow to allocate... (14 Replies)
Hi,
I am trying to use "find / -name core -print | xargs rm -f " ,but it would delete all core files including some core files we do not want to delete.
I search privious posts,someone said "To check what a core file came from - use the file command"
I used man page to search file command,but... (9 Replies)
hi all,
I am having set of core dumps obtained from client server. Now i am trying to read them but unable to do so.
I have few queries:
1. Core dumps were generated on some xyz server and copied to my unix virtual. Can I read them as text here?
2. I tried installing gdb-7.3 but when i fire... (0 Replies)
Discussion started by: suyogs
0 Replies
LEARN ABOUT HPUX
gcore
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)