06-09-2009
the same c++ code is running without errors in other machines. i checked the same code in a sunOS 5.9 machine and in an AIX 5 machine. Its not giving the error in those machines. This error is with this one machine only. checked the c++ code as u suggested by including logs. execution of a function is returning a success, but the returned success is not caught at the calling function and is giving the core exactly there. what may be the reason and what can be done for this ?
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. Solaris
Greetings,
This is my first post here. I am using a library based on Net-SNMP in TCL scripts. The person who developed the library has disappeared and I don't have the source code. When the script is running on one UNIX workstation, core dump happens from time to time but it works well on... (0 Replies)
Discussion started by: chongkaijiang
0 Replies
3. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
4. Solaris
Hi, im getting a core dump file in my sun OS version 5.9 while using a complex c++ program. The same program is working without any core error in another system with same sun OS and same version. The program has used structs, LL's and lots of call by references. What may be the reason. will it be a... (3 Replies)
Discussion started by: suresh_kb211
3 Replies
5. Programming
Hi, I am running a c++ program in unix sun OS 5.9. There are two functions in a file which are being used by a third function in the same file. the two functions being used are of the same type. one function is returning a success and the control is redeemed by the calling function. for teh second... (2 Replies)
Discussion started by: suresh_kb211
2 Replies
6. Programming
Hi, I am running a c++ program in unix sun OS 5.9. There are two functions in a file which are being used by a third function in the same file. the two functions being used are of the same type. one function is returning a success and the control is redeemed by the calling function. for teh second... (5 Replies)
Discussion started by: suresh_kb211
5 Replies
7. Programming
Posting again, as previous query had a typo.
=======================================================
Hi, I am running a c++ program in unix AIX machine. There are two functions in a file which are being used by a third function in the same file. the two functions being used are of the same type.... (1 Reply)
Discussion started by: suresh_kb211
1 Replies
8. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
9. AIX
Hi There,
I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available).
Anyone could provide me the following answer -
Can IBM VM been deploy on X86 and X64 (Intel Chip)?
If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
10. UNIX for Dummies Questions & Answers
Hi
I am using Linux and I am using Java as well as C++ services running on it.
The ulimit -c is set to around 400Mb.
Whenever any of the service fails they produce a core file.(Actual size of core could be greater than 400Mb).
Whenever my Java service fails I get a core file of size 400Mb... (3 Replies)
Discussion started by: Raj999
3 Replies
CORE(5) BSD File Formats Manual CORE(5)
NAME
core -- memory image file format
SYNOPSIS
#include <sys/param.h>
DESCRIPTION
A small number of signals which cause abnormal termination of a process also cause a record of the process's in-core state to be written to
disk for later examination by one of the available debuggers. (See sigaction(2).) This memory image is written to a file named by default
programname.core in the working directory; provided the terminated process had write permission in the directory, and provided the abnormal-
ity did not cause a system crash. (In this event, the decision to save the core file is arbitrary, see savecore(8).)
The maximum size of a core file is limited by setrlimit(2). Files which would be larger than the limit are not created.
The name of the file is controlled via the sysctl(8) variable kern.corefile. The contents of this variable describes a filename to store the
core image to. This filename can be absolute, or relative (which will resolve to the current working directory of the program generating
it).
The following format specifiers may be used in the kern.corefile sysctl to insert additional information into the resulting core file name:
%H Machine hostname.
%I An index starting at zero until the sysctl debug.ncores is reached. This can be useful for limiting the number of corefiles
generated by a particular process.
%N process name.
%P processes PID.
%U process UID.
The name defaults to %N.core, yielding the traditional FreeBSD behaviour.
By default, a process that changes user or group credentials whether real or effective will not create a corefile. This behaviour can be
changed to generate a core dump by setting the sysctl(8) variable kern.sugid_coredump to 1.
Corefiles can be compressed by the kernel if the following items are included in the kernel configuration file:
options COMPRESS_USER_CORES
devices gzio
When COMPRESS_USER_CORES is included the following sysctls can control if core files will be compressed:
kern.compress_user_cores_gzlevel Gzip compression level. Defaults to -1.
kern.compress_user_cores Actually compress user cores. Core files will have the suffix .gz appended to them.
EXAMPLES
In order to store all core images in per-user private areas under /var/coredumps, the following sysctl(8) command can be used:
sysctl kern.corefile=/var/coredumps/%U/%N.core
SEE ALSO
gdb(1), kgdb(1), setrlimit(2), sigaction(2), sysctl(8)
HISTORY
A core file format appeared in Version 6 AT&T UNIX.
BSD
November 22, 2012 BSD