10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
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
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
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
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
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
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
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
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
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
ipcs(1) General Commands Manual ipcs(1)
NAME
ipcs - Reports Interprocess Communication (IPC) facility status
SYNOPSIS
ipcs [-a | -bcopt] [-mqs] [-C corefile] [-N namelist]
The ipcs command writes to the standard output information about active Interprocess Communication (IPC) facilities.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
ipcs: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
Same as specifying the -b, -c, -o, -p, and -t options. Writes the maximum number of bytes in message queues, the size of segments for
shared memory, and the number of semaphores in each semaphore set. Writes the username and group name of the user that made the facility.
Writes report based on contents of file corefile instead of /dev/kmem. Writes information about active shared memory segments. Writes
report based on contents of file namelist instead of /vmunix. Writes the following usage information: Number of messages on queue Total
number of bytes in message queues Number of processes attached to shared memory segments Writes the following: Process number of the last
process to receive a message on message queues Process number of the creating process Process number of last process to attach or detach on
shared memory segments Writes information about active message queues. Writes information about active semaphore set. Writes the follow-
ing: Time of the last control operation that changed the access permissions for all facilities Time of the last msgsnd() and last msgrcv()
on message queues Time of the last shmat() and last shmdt() on shared memory Time of the last semop() on semaphore sets
DESCRIPTION
If you do not specify any options, ipcs writes information in a short form about currently active message queues, shared memory segments,
semaphores, remote queues, and local queue headers.
Column Headings
The column headings and the meaning of the columns in an ipcs listing follow. The letters in parentheses indicate the flags that cause the
corresponding heading to appear. The word all means that the heading always appears. The flags only determine what information is pro-
vided for each facility; they do not determine which facilities are listed. Type of facility: Message queue Shared memory segment Sema-
phore The identifier for the facility entry. The key used as a parameter to the msgget(), semget() or shemget() system calls to make the
facility entry.
Note that the key of a shared memory segment is changed to IPC_PRIVATE when the segment is removed. This change remains in effect
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: [Tru64 UNIX] If the associated shared memory segment was locked. If a process is waiting on a
msgrcv() system call. If a process is waiting on a msgsnd() system call. If the associated shared memory segment was removed. It
disappears when the last process attached to the segment detaches it. If the corresponding special flag is not set.
The next nine characters are interpreted as three sets of three bits each. The first set refers to the owner's permissions, the
next to permissions of others in the user group of the facility entry, and the last to all others. Within each set, the first char-
acter indicates permission to read, the second character indicates permission to write or alter the facility entry, and the last
character is currently unused.
The permissions are indicated as follows: Read permission is granted. Write permission is granted. Alter permission is granted.
The indicated permission is not granted. The username of the owner of the facility entry. The name of the group that owns the
facility entry. The username of the creator of the facility entry. The group name of the group of the creator of the facility
entry.
Note that for the OWNER, GROUP, CREATOR, and CGROUP, the user and group IDs display instead of the usernames. 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 ID of the last
process that sent a message to the associated queue. The ID of the last process that received a message from the associated queue.
The time when the last message was sent to the associated queue. The time when the last message was received from the associated
queue. The time when the associated 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 creator of the shared memory entry. The process
ID of the last process to attach or detach the shared memory segment. The time when the last attach was completed to the associated
shared memory segment. The time when the last detach was completed on the associated shared memory segment. The number of sema-
phores in the set associated with the semaphore entry. The time when the last semaphore operation was completed on the set associ-
ated with the semaphore entry.
EXAMPLES
Sample output from entering ipcs without options follows.
Message Queues:
T ID KEY MODE OWNER GROUP
q 4 0x41002ab4 --rw------- root system
Shared Memory:
T ID KEY MODE OWNER GROUP
m 0 0x3253bc5c --rw-rw-rw- root system
m 129 0 DLrw------- root daemon
Semaphores:
T ID KEY MODE OWNER GROUP
s 0 0x41002ab4 --ra------- root system
Output is formatted differently if the environment variable CMD_ENV is set to the string svr4. For example:
IPC status from /dev/kmem as of Thu Mar 26 11:31:03 1998
T ID KEY MODE OWNER GROUP
Message Queues:
q 4 0x41002ab4 --rw------- root system
Shared Memory:
m 0 0x3253bc5c --rw-rw-rw- root system
m 129 0 DLrw------- root daemon
Semaphores:
s 0 0x41002ab4 --ra------- root system
FILES
Contains user information. Contains group information.
SEE ALSO
Commands: ipcrm(1)
Functions: msgrcv(2), msgsnd(2), semop(2), shmat(2), shmdt(2)
ipcs(1)