Abort core dumped!!!!


 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory Abort core dumped!!!!
Prev   Next
# 1  
Old 07-07-2003
Data Abort core dumped!!!!

HI All,

I am working on Solaris 8, i have this application runing on one of the partitions,(the installation was done here ie /export/home)

And the out put of this goes to another parition of other disk attached to the same machine. After a certain period of time is get this error stating "Abort core dumped". When i checked the core file the message read as "swapfile only valid if -k".

What could be the problem. Is it that the partitin on which the files are getting created is not mounted with proper options(cos earlier also i have ran the application with equal amount of data but then the output was on the same partition and also i had unmounted the parition whcih is storing the output now and mounted it back again).

Thanks in advance
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

(core dumped) | gjar

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

2. Solaris

Segmentation Fault (core dumped)

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

3. Programming

Memory Fault,Core dumped

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

4. UNIX for Advanced & Expert Users

Memory Fault - Core Dumped

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

5. UNIX for Advanced & Expert Users

examine core file after abort()

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

6. BSD

stack overflow in function psync_status Abort (core dumped)

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

7. Programming

Segmentation Fault (core dumped)

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

8. UNIX for Advanced & Expert Users

Bus Error Core Dumped

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

9. UNIX for Dummies Questions & Answers

core dumped

what is segmentation core dumped? how should i respond? (9 Replies)
Discussion started by: yls177
9 Replies

10. UNIX for Dummies Questions & Answers

Segmentation fault (core dumped)

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
Login or Register to Ask a Question
gcore(1)						    BSD General Commands Manual 						  gcore(1)

NAME
gcore -- get core images of running processes SYNOPSIS
gcore [-s] [-v] [-b size] [-o path | -c pathformat] pid DESCRIPTION
The gcore program creates a core file image of the process specified by pid. The resulting core file can be used with a debugger, e.g. lldb(1), to examine the state of the process. The following options are available: -s Suspend the process while the core file is captured. -v Report progress on the dump as it proceeds. -b size Limit the size of the core file to size MiBytes. The following options control the name of the core file: -o path Write the core file to path. -c pathformat Write the core file to pathformat. The pathformat string is treated as a pathname that may contain various special characters which cause the interpolation of strings representing specific attributes of the process into the name. Each special character is introduced by the % character. The format characters and their meanings are: N The name of the program being dumped, as reported by ps(1). U The uid of the process being dumped, converted to a string. P The pid of the process being dumped, converted to a string. T The time when the core file was taken, converted to ISO 8601 format. % Output a percent character. The default file name used by gcore is %N-%P-%T. By default, the core file will be written to a directory whose name is determined from the kern.corefile MIB. This can be printed or modified using sysctl(8). The directory where the core file is to be written must be accessible to the owner of the target process. gcore will not overwrite an existing file, nor will it create missing directories in the path. EXIT_STATUS The gcore utility exits 0 on success, and >0 if an error occurs. FILES
/cores/%N-%P-%T default pathname for the corefile. BUGS
With the -b flag, gcore writes out as much data as it can up to the specified limit, even if that results in an incomplete core image. Such a partial core dump may confuse subsequent programs that attempt to parse the contents of such files. SEE ALSO
lldb(1), core(5), Mach-O(5), sysctl(8), sudo(8). Darwin May 31, 2019 Darwin