07-10-2003
HI Hoghunter,
What command are you using to check the file?
I am using Exceed which is gui to my unix server.in exceed i have to right click and i get some options, one of them is "Show Stack using adb", this opens the core file and displays the message.
Is this a system dump or just a core file from the application?
The core file is from the application(it got created in the application's folder, i guess it is from the app. How do you know a system dump?)
What is the application?
The application is actually a reporting software.(Actuate)
The core dump is from the Application.
Zing
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello To All!
Now anfd then I receive a message on my console:
Segmentation fault (core dumped)
What does it mean? Or more precisely what are the implications?
:confused: (1 Reply)
Discussion started by: Ivo
1 Replies
2. UNIX for Dummies Questions & Answers
what is segmentation core dumped?
how should i respond? (9 Replies)
Discussion started by: yls177
9 Replies
3. UNIX for Advanced & Expert Users
I faced following problem while restoring root backup
Server : Compaq Proliant 6000
OS SCO : Unixware 7.0
#tar - xvf /dev/rmt/ctape1
After extracting some files following error message occurred and process stopped
# BUS ERROR CORE DUMPED
What may be the problem? How to avoid... (1 Reply)
Discussion started by: j1yant
1 Replies
4. Programming
what r the situations to receive an error msg like the one below
Segmentation Fault (core dumped) (2 Replies)
Discussion started by: bankpro
2 Replies
5. BSD
I am running Open BSD 3.8 (3.5 upgrade) on a Pent Pro. 200, 64 Megs Ram, Nvedia Vanta TNT 16 Megs, Realtech 8139 Nic. When running ifconfig -a I get this error back. I've run searches on google no deal. I can get Stack overflow or psync, but not both. So I would really like to know how to fix it. ... (0 Replies)
Discussion started by: jmcpreach
0 Replies
6. UNIX for Advanced & Expert Users
I'm running Red Hat Linux 2.6.7 on a x86_64 box.
I have a core file from a program that called abort(). Does anyone here know how can I get a backtrace? (Re-creating the error with svd running inside gdb has proved impossible).
% gdb svd core.25223
GNU gdb Red Hat Linux... (2 Replies)
Discussion started by: svact
2 Replies
7. UNIX for Advanced & Expert Users
I use SCO UNIX 5.07 on a Compaq Proliant Machine. Each time I press the Escape or Delete key while running a program or issuing a FoxBase+ command from the dot prompt, I receive the error message: "Memory Fault - Core Dumped" and the screen locks up immediately.
I would appreciate if necessary... (0 Replies)
Discussion started by: bayuz
0 Replies
8. Programming
I have written a code in UNIX which is complied by using g++. Compling with turbo C didnt yield any errors, but with g++ I am getting Memory fault, core dumped. Could anyone help me out with this?
Given below is the code:
#include<stdio.h>
#include<string.h>
#include<stdlib.h>... (2 Replies)
Discussion started by: usshell
2 Replies
9. Solaris
i am getting Segmentation Fault (core dumped) on solaris,
but when i run the same program with same input on linux it runs successfully.
How can i trace the fault in program on solaris. (6 Replies)
Discussion started by: junaid.nehvi
6 Replies
10. Filesystems, Disks and Memory
hello,
when i make gcc 4.4.2 i get this message
find gnu java javax org sun -name .svn -prune -o -name '*.class' -print | \
gjar -cfM@ $here/libgcj-4.4.2.jar
/bin/sh: line 2: 32730 Done find gnu java javax org sun -name .svn -prune -o -name '*.class'... (2 Replies)
Discussion started by: aleppos
2 Replies
SAVECORE(8) System Manager's Manual SAVECORE(8)
NAME
savecore - save a core dump of the operating system
SYNOPSIS
savecore dirname [ system ]
DESCRIPTION
Savecore is meant to be called at the end of the /etc/rc file. Its function is to save the core dump of the system (if one was made) and
to write a reboot message in the shutdown log.
It saves the core image in the file dirname/core.n and its corresponding namelist in dirname/unix.n. The second argument is the namelist
for the system which made the core image; the current system is always assumed to be /unix. The trailing ".n" in the pathnames is replaced
by a number which grows every time savecore is run in that directory.
Before savecore writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the file sys-
tem which contains dirname than the number obtained from the minfree file, the core dump is not done. If the minfree file does not exist,
savecore always writes out the core file (assuming that a core dump was taken).
Savecore also writes a reboot message in the shut down log. If the system crashed as a result of a panic, savecore records the panic
string in the shut down log too.
If savecore detects that the system time is wrong because of a crash (the time in the core image is after the current time), it will reset
the system time to its best estimate of the time, which is the time in the core image plus the elapsed time since the reboot. It announces
the time that it set when this occurs.
FILES
/usr/adm/shutdownlogshutdown log
/unix current UNIX
BUGS
The method used to determine whether a dump is present, and to prevent the same core image from being saved multiple times, is not elegant.
This information should be passed to init by the system; however, this is difficult because the system may have to be rebooted a second
time if the root filesystem is patched.
3rd Berkeley Distribution SAVECORE(8)