01-17-2008
If you have the core file you can start with a "pstack core" to see what the application was doing at 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? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Advanced & Expert Users
I am importing data into a new database using bcp (ASE 11.0) on Solaris 5.7. I keep getting a core dump error when my ksh script attempts to load one table. All other tables load fine. If I load the table directly from the command line without a script the table loads fine.
Does anybody know... (1 Reply)
Discussion started by: gerald_agoi
1 Replies
3. UNIX for Dummies Questions & Answers
does any one have read a core dump?
is there any reader for that? or may i know what is the use of that core which takes sometimes memory in GBs?
:) (6 Replies)
Discussion started by: sskb
6 Replies
4. UNIX for Dummies Questions & Answers
Hi ,
Working on AIX 4.3. An internal error from my apps engine suddenly causes the engine to die. During this time i do notice a core file being dumped in the directory from where I try to re-start my engine.
Q is how does one read this core file, or I should say 'what is this core file'?
thnx (2 Replies)
Discussion started by: buRst
2 Replies
5. 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
6. Programming
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
7. UNIX for Advanced & Expert Users
Hello all,
Iam new to unix while executing java program which finely working in windows know iam testing with unix ,but in unix while executing iam getting core dump, my application is in client server environment and it is menu drivrn application on clicking options no problem but after some time... (1 Reply)
Discussion started by: vinp
1 Replies
8. Solaris
There's something strange with fmd in update 6. On four identical machines (Netra T2000) all installed thru jumpstart (same configuration, same packages, same patches, same firmware) fmd randomly refuses to start after reboot.
$ cat /var/svc/log/system-fmd:default.log
...
$ svcs... (8 Replies)
Discussion started by: Luka
8 Replies
9. Solaris
I have compiled GhostPDL that provides a shell script pcl2pdf that calls the executable pcl6.
pcl6 compiled with no errors using gmake and gcc. Running pcl2pdf generates a core dump when trying to convert a pcl file to pdf.
I have installed the Ghost fonts. Does anyone have GhostPDL compiled... (1 Reply)
Discussion started by: gduncan
1 Replies
10. Shell Programming and Scripting
Hi All,
I am doing Solaris packaging. I got core dump error while doing it. I have identified particular folder causing it but not sure about the reason. Without
that folder i can able to do the package. I have attached the proto file and other related files for your reference. Pls... (1 Reply)
Discussion started by: kamal_456
1 Replies
coreadm(2) System Calls Manual coreadm(2)
NAME
coreadm - application core file administration
SYNOPSIS
DESCRIPTION
system call is used to specify the location and pattern for core files produced by abnormally terminating processes. See core(4). This
system call can be used to specify a system wide location for core file placement and/or a process specific pattern.
The structure, is used to specify a system wide or a per-process core file pattern and also specify the current system wide core file set-
tings. is defined in the header
Member Type Member Name Description
char c_pattern The core file pattern.
uint64_t c_flags Core file settings.
Parameters
is expected to be set to It is critical for future backward compatibility that the macro itself be used and not its value.
is the core file pattern. A core file name pattern is a normal file system path name with embedded variables, specified with a leading
character, that are expanded from values in effect when a core file is generated by the operating system. An expanded pattern length
greater than will be truncated to
The possible values are:
c_flags is used to control the system wide core file settings. The flag values can be combination of
Enable/Disable creation of global core files.
Enable/Disable creation of per-process core files.
Enable/Disable creation of global core files for
processes.
Enable/Disable creation of per-process core file for
processes.
If a flag value is not set, then the option is disabled.
For per-process core file setting, c_flags can either be 0 or The former disables core file creation (for that process) and the latter
enables it.
c_pid Should be a (valid) pid of a target process or 0. If c_pid is zero, then the settings are applied to global core file settings.
If c_pid is 1, then the settings are applied to init(1M).
c_in If non-NULL, then the values will be used as new core file settings. If this is NULL, then the c_out parameter is expected to be
non-NULL and system call is used to interrogate the current settings.
c_out If non-NULL, the current settings are returned in this parameter.
RETURN VALUE
Upon successful completion, returns 0. Otherwise, a value of -1 is returned and is set to indicate the error.
ERRORS
fails and does not change the core file settings if
the effective user-ID of the calling process is not a user having appropriate privileges.
The input or output parameter passed to
is an invalid address.
The core file pattern or flags is invalid.
The specified PID is non-zero and does not exist.
EXAMPLES
1. Enable global core file creation using the pattern (core.process-ID.machine-name) in the location
2. Enable per-process core file pattern for the process-ID passed in as argument. The core file will be placed in The pattern is
(core.process-ID.time-stamp).
3. Enable a per-process pattern of core.CUP-ID for all processes in the system (init(1M) core file setting). NOTE: This has to be run
during system startup or reboot the machine after setting this for the settings to take full effect.
SEE ALSO
coreadm(1M), exec(2), fork(2), pstat(2), ttrace(2), core(4).
STANDARDS CONFORMANCE
coreadm(2)