Memory fault(coredump)


 
Thread Tools Search this Thread
Top Forums Programming Memory fault(coredump)
# 1  
Old 10-14-2005
Memory fault(coredump)

Dear All,

I made a program which do some simple jobs like reading data from other process's shared memory and writing messages to the queues of other process.

what happens is my program works fine and do all the task as expected but then then program ends it give Memory fault(coredump). I cannot figure out why.

Looking forward for you replies.

Regards.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Memory fault(Coredump)

Hi, In my application we have one job which is used to process the files. But that job is failing with memory fault while processing a file or while shutting down the job. Sometime it generates the coredump and sometimes not. When I analysed the core dump I got below code snippet where it... (3 Replies)
Discussion started by: shilpa_20
3 Replies

2. Homework & Coursework Questions

Memory fault(coredump)

I am writing a program that copies a program and prints the program with a line count. this is the program I wrote: #include <stdio.h> main() { int c; int nl_cnt = 0; while((c = getchar()) != EOF){ if(c = '\n'){ nl_cnt++;... (3 Replies)
Discussion started by: heywoodfloyd
3 Replies

3. AIX

Error: Memory fault(coredump)

Hi Experts, While running a command, i saw this error below # ls -lrt total 74008 -rw-r--r-- 1 rr57104 edcfes 37889134 May 16 12:41 LGTOnw.clnt.7.4.2.0.bff.tar.gz drwxr-xr-x 2 root system 256 May 18 12:42 lost+found # gunzip LGTOnw.clnt.7.4.2.0.bff.tar.gz Memory fault(coredump) ... (2 Replies)
Discussion started by: EngnrRG
2 Replies

4. Shell Programming and Scripting

Memory fault(coredump) while using cat cmd

i have few log files that are input to my perl script... i am executing the script as below cat RTR*.log | test.pl and getting the following error -ksh: 25014: Memory fault(coredump) cat: write error: Connection reset by peer can anyone help me on this.... Thanks in... (2 Replies)
Discussion started by: niteesh_!7
2 Replies

5. Programming

Memory fault(coredump) while using Environment variables

Hi, Actually I am facing one issue while using the getenv() in the C/C++ program. I want to take the file path from environment variables and if am not defining the environment path, its showing the message like this…! Memory fault(coredump) Actually I want to handle the error ,... (6 Replies)
Discussion started by: Kattoor
6 Replies

6. Shell Programming and Scripting

Segmentation Fault(coredump)

I'm getting this error when trying to run a Acucobol program thru UNIX.. Segmentation Fault(coredump) Precompiler error prevents compilation of xxxxxx.co. Please help me in this case.. (1 Reply)
Discussion started by: Manish4
1 Replies

7. Solaris

memory fault (coredump)

Getting memory fault (coredump) and segmentation fault(coredump) when i tried javac or java -version. what could be the problem? Regards Eswar (2 Replies)
Discussion started by: BhuvanEswar
2 Replies

8. Ubuntu

Memory fault(coredump)

Hey guys, I am new to the Linux world and have a question to post. When I ssh from a HP-UX machine to a ubuntu machine I get the following error message Memory fault(coredump) i.e. ssh 192.168.1.3 I get this message as shown below Memory fault(coredump) Can someone please explain... (2 Replies)
Discussion started by: fkaba81
2 Replies

9. AIX

Segmentation fault(coredump)

Hi All Can anybody help me? When ever am trying to run topas system gives me an error Segmentation fault(coredump) does anybody ahve solution for this? (4 Replies)
Discussion started by: vjm
4 Replies

10. UNIX for Dummies Questions & Answers

Coredump (memory fault)

We are running a SQR program on Unix Platform with Oracle RDBMS. It's an interfacing program to integrate data from foreign sites to PeopleSoft database, using a flat file input. After many hours of processing, the program stops with a coredump error (memory fault). With top command we noticed... (1 Reply)
Discussion started by: araziki
1 Replies
Login or Register to Ask a Question
ipcs(1) 						      General Commands Manual							   ipcs(1)

NAME
ipcs - report status of interprocess communication facilities SYNOPSIS
core] namelist] DESCRIPTION
displays certain information about active interprocess communication facilities. With no options, displays information in short format for the message queues, shared memory segments, and semaphores that are currently active in the system. Options The following options restrict the display to the corresponding facilities. (none) This is equivalent to Display information about active shared memory segments. Display information about active message queues. Display information about active semaphores. The following options add columns of data to the display. See "Column Description" below. (none) Display default columns: for all facilities: Display all columns, as appropriate. This is equivalent to Display largest-allowable-size information: for message queues: for shared memory segments: for semaphores: Display creator's login name and group name: for all facilities: Display information on outstanding usage: for message queues: for shared memory segments: Display process number information: for message queues: for shared memory segments: Display time information: for all facilities: for message queues: for shared memory segments: for semaphores: The following options redefine the sources of information. Use core in place of core can be a core file or a directory created by or Use file namelist or the namelist within core in place of It opens a crash dump for reading. Please refer to cr_open(3) for more details. Column Descriptions The column headings and the meaning of the columns in an listing are given below. The columns are printed from left to right in the order shown below. Facility type: Shared memory segment Message queue Semaphore The identifier for the facility entry. The key used as an argument to or to create the facility entry. (Note: The key of a shared memory segment is changed to when the segment has been removed until all processes attached to the segment detach it.) The facility access modes and flags: The mode consists of 11 characters that are interpreted as follows: The first two characters can be: A process is waiting on a A process is waiting on a The associated shared memory segment has been removed. It will disappear when the last process attached to the segment detaches it. The associated shared memory segment is to be cleared when the first attach is executed. The corresponding special flag is not set. The next 9 characters are interpreted as three sets of three characters each. The first set refers to the owner's permissions, the next to permissions of others in the group of the facility entry, and the last to all others. Within each set, the first character indicates permission to read, the second character indicates permission to write or alter the facility entry, and the last character is currently unused. Read permission is granted. Write permission is granted. Alter permission is granted. The indicated permission is not granted. The login name of the owner of the facility entry. The group name of the group of the owner of the facility entry. The login name of the creator of the facility entry. The group name of the group of the creator of the facility entry. The number of bytes in messages currently outstanding on the associated message queue. The number of messages currently outstanding on the associated message queue. The maximum number of bytes allowed in messages outstanding on the associated message queue. The process ID of the last process to send a message to the associated message queue. The process ID of the last process to receive a message from the associated message queue. The time the last message was sent to the associated message queue. The time the last message was received from the associated message queue. The time when the associated facility entry was created or changed. The number of processes attached to the associated shared memory segment. The size of the associated shared memory segment. The process ID of the creating process of the shared memory segment. The process ID of the last process to attach or detach the shared memory segment. The time the last attach was completed to the associated shared memory segment. The time the last detach was completed on the associated shared memory segment. The number of semaphores in the set associated with the semaphore entry. The time the last semaphore operation was completed on the set associated with the semaphore entry. WARNINGS
produces only an approximate indication of actual system status because system processes are continually changing while is acquiring the requested information. Do not rely on the exact field widths and spacing of the output, as these will vary depending on the system, the release of HP-UX, and the data to be displayed. FILES
Kernel virtual memory Group names User names System namelist SEE ALSO
msgop(2), semop(2), shmop(2). STANDARDS CONFORMANCE
ipcs(1)