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 - report interprocess communication facilities status
Syntax
ipcs [options]
Description
The command provides information about active, interprocess communication facilities, message queues, shared memory, and semaphores that
are currently active in the system.
Options
The information is displayed in columns and is controlled by the following options:
-m Displays information about active shared memory segments
-q Displays information about active message queues
-s Displays information about active semaphores
If any of the options -q, -m, or -s are specified, information about only those indicated are printed. If none of these three is speci-
fied, information about all three are printed.
-a Uses all print options (shorthand notation for -b, -c, -o, -p and -t)
-b Displays the biggest allowable size information (maximum number of bytes in messages on queue for message queues, size of segments
for shared memory, and number of semaphores in each set for semaphores)
-C Uses the specified core file (next argument) in place of
-c Displays creator's login name and group name
-N Uses the specified namelist (next argument) in place of
-o Displays the outstanding usage information (number of messages in queue, size of each and number of processes attached to shared
memory segments)
-p Displays the process ID information (process ID of last process to send a message and process ID of last process to receive a mes-
sage on message queues and process ID of creating process and process ID of last process to attach or detach on shared memory seg-
ments)
-t Displays all time statistics (time of the last control operation that changed the access permissions for all facilities, time of
last and last on message queues, last and last on shared memory, last on semaphores)
The column headings and the meaning of the columns in an listing are given below. The letters in parentheses indicate the options that
cause the corresponding heading to appear; all means that the heading always appears. Note that these options only determine what informa-
tion is provided for each facility; they do not determine which facilities are listed.
T (all) Type of facility:
q Message queue
m Shared memory segment
s Semaphore
ID (all) The identifier for the facility entry.
KEY (all) The key used as an argument to or to create the facility entry. Note: The key of a shared memory segment is changed
to IPC_PRIVATE when the segment has been removed until all processes attached to the segment detach it.
MODE (all) The facility access modes and flags.
The mode consists of 11 characters. The first two characters are interpreted as follows:
R If the process is waiting on a
S If a process is waiting on a
D If the associated shared memory segment has been removed. It disappears when the last process attached to the
segment detaches it.
C If the associated shared memory segment is to be clear when the first attach is executed.
- If the corresponding special flag is not set.
The next 9 characters are interpreted as three sets of three bits each. The first set refers to the owner's permis-
sions; 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 character indicates permission to write or alter the facility entry, and the last character is cur-
rently unused.
The permissions are indicated as follows:
r If read permission is granted
w If write permission is granted
a If alter permission is granted
- If the indicated permission is not granted
OWNER (all) The login name of the owner of the facility entry.
GROUP (all) The group name of the group of the owner of the facility entry.
CREATOR (a,c) The login name of the creator of the facility entry.
CGROUP (a,c) The group name of the group of the creator of the facility entry.
CBYTES (a,o) The number of bytes in messages currently outstanding on the associated message queue.
QNUM (a,o) The number of messages currently outstanding on the associated message queue.
QBYTES (a,b) The maximum number of bytes allowed in messages outstanding on the associated message queue.
LSPID (a,p) The process ID of the last process to send a message to the associated queue.
LRPID (a,p) The process ID of the last process to receive a message from the associated queue.
STIME (a,t) The time the last message was sent to the associated queue.
RTIME (a,t) The time the last message was received from the associated queue.
CTIME (a,t) The time the associated entry was created or changed.
NATTCH (a,o) The number of processes attached to the associated shared memory segment.
SEGSZ (a,b) The size of the associated shared memory segment.
CPID (a,p) The process ID of the creator of the shared memory entry.
LPID (a,p) The process ID of the last process to attach or detach the shared memory segment.
ATIME (a,t) The time the last attach was completed to the associated shared memory segment.
DTIME (a,t) The time the last detach was completed on the associated shared memory segment.
NSEMS (a,b) The number of semaphores in the set associated with the semaphore entry.
OTIME (a,t) The time the last semaphore operation was completed on the set associated with the semaphore entry.
Restrictions
Things can change while is running. The picture it gives is only a close approximation to reality.
Files
/vmunix system namelist
/dev/kmem memory
/etc/passwd user names
/etc/group group names
See Also
ipcrm(2), msgop(2), semop(2), shmop(2)
ipcs(1)