Sponsored Content
Full Discussion: Memory Fault
Top Forums UNIX for Dummies Questions & Answers Memory Fault Post 18919 by Bab00shka on Thursday 4th of April 2002 08:09:14 AM
Old 04-04-2002
Hi

This happens when there is some sort of conflict within memory. A file called "core" is produced. This contains an image of the memory at the time the problem occurred. There are packages available to examine the "core" file to find out where the memory conflict occurs. But, its not always easy to trace the error.

There could be numerous reasons why this is happening. It could be that he application could require permissions or environment variables which are only available to the superuser. Although it may be just "luck" that the core dump does not happen as "superuser", such is the nature of memory faults. Do you have the source code to the application? If so, it may be worth checking the permissions/env variables theory within the code. It could also be a totally unrelated error in the source code.

Sorry to be vague, but memory faults are unpredictable by nature and difficult to track down without usually a great deal of investigation.

Good luck!
 

10 More Discussions You Might Find Interesting

1. Programming

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... (0 Replies)
Discussion started by: ralo
0 Replies

2. Programming

memory fault

When I excute a program . It seems to generate an error : memory fault (core dump ) So how can i (1 Reply)
Discussion started by: iwbasts
1 Replies

3. UNIX for Advanced & Expert Users

Memory fault in ql session

Hi, Am getting memory fault when i start ql session in SCO unix server. Can any one suggest the way to solve this issue. Thanks (0 Replies)
Discussion started by: param_it
0 Replies

4. 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

5. UNIX for Dummies Questions & Answers

mysql memory fault

I (think I) installed MYSQL on a Red Hat box. When I try to start mysql I get a memory fault error. Any ideas on how to fix this? Here is some info that might help: My distro info $ cat /proc/version Linux version 2.4.21-40.ELsmp (bhcompile@hs20-bc1-7 .build.redhat.com) (gcc version 3.2.3... (0 Replies)
Discussion started by: wsetchell
0 Replies

6. UNIX for Advanced & Expert Users

Setui(0) memory fault

Hi i have this code that used to wrok fine in unix mp-ras. After the migration to linux suse i recompiled the script and now when it is executed i get a Memory fault (coredump) message. Does anybody knows why' what should I change? tks SCRIPT #include <stdio.h> #include <sys/types.h>... (1 Reply)
Discussion started by: mrodrig
1 Replies

7. Linux

Help with memory fault

We have migrated our application from HP UX to linux. The code is in 4gl and after migration it has started giving Memory fault while running a batch job. The trace shows segmentation fault after a series of recvfrom and sendto(DB read) sigsegv segmentation fault @ 0 0 killed by SIGSEGV The... (2 Replies)
Discussion started by: aimee
2 Replies

8. UNIX for Dummies Questions & Answers

Page Fault + Memory

I am not sure where to post this so i will put it in the newbie section. I have set up a bog standard debain 6, LAMP environment in the cloud. The specs 1 core at 2GH 2.5gb Memory running Jommla, with about 1.6K visitors a day. I am using AppFirst (appfirst.com) to monitor the... (2 Replies)
Discussion started by: waseem
2 Replies

9. 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

10. Solaris

M4000 Memory Fault

Hi Guys and Gals, Does anyone know how to track down a faulty DIMM on the memory board of an M4000? showhardconf tells me which board it is, but was wondering if there was a way to track it down to a DIMM? Thanks in advance Martin (5 Replies)
Discussion started by: callmebob
5 Replies
crashutil(1M)															     crashutil(1M)

NAME
crashutil - manipulate crash dump data SYNOPSIS
version] source [destination] DESCRIPTION
copies and preserves crash dump data, and performs format conversions on it. Common uses of include: o Copying portions of a dump that still reside on a raw dump device into a crash dump directory. o Converting between different formats of crash dumps. o Copying crash dumps from one directory, or medium, to another. will write to its destination the crash dump it reads from its source. The crash dump format used to write the destination is specified with if is not specified, the destination will have the same format as the source. If no destination is specified, source is used; the format conversion will be done in place in the source, without copying. When completes successfully, the entire contents of the crash dump will exist at destination; any portions that had still been on raw dump devices will have been copied to destination. There are three known dump formats: (Version 0) This format, used up through HP-UX 10.01, consists of a single file containing the physical memory image, with a 1-to-1 cor- respondence between file offset and memory address. Normally there is an associated file containing the kernel image. sources or destinations of this type must be specified as two pathnames to plain files, separated by whitespace; the first is the core image file and the second is the kernel image file. (Version 1) This format, used in HP-UX 10.10, 10.20, and 10.30, consists of a directory containing an file, the kernel file, and numerous files, which contain portions of the physical memory image. sources or destinations of this type should be specified as the pathname to a core directory. (Version 2) This format, used in HP-UX 11.00 and later, consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which were not. sources or destinations of this type should be specified as the pathname to a crash directory. (Version 3) This format is used in HP-UX Release 11i Version 1.0 and later. It is very similar in structure to the format in that it consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which were not. In addition to the primary file, there are auxiliary index files, that contain metadata describing the image files containing the memory pages. This format will be used when the dump is compressed. See crashconf(1M). Other formats, for example tape archival formats, may be added in the future. When the source and destination are different types of files -- for example, when source is a directory and destination is a pair of plain files -- both must be specified. Options (Quiet) Disables the printing of progress messages. Warning and error messages are still printed. Specifies the version of the destination format. Allowed values are 0, 1, 2 or 3. Also allowed is the keyword which specifies that the destination format should be the same as the current source format. is the default if is not specified. If the destination format is then the source format should also be Conversion to from older formats is not supported. RETURN VALUE
Upon exit, returns the following values: 0 The operation was successful. 1 The operation failed, and an appropriate error message was printed. EXAMPLES
An HP-UX 11.00 crash dump was saved by savecrash(1M) to The flag was specified to savecrash, specifying that only those portions of the dump which were endangered by swap activity should be saved; the rest are still resident in the raw dump devices. To save the remainder of the dump into the crash dump directory, use: If preferred, the completed crash dump directory could be in a different location -- perhaps on another machine via NFS: To debug this crash dump using tools which do not understand the most current crash dump format, convert it to the older core directory format: or the even older "core file and kernel" format: AUTHOR
was developed by HP. SEE ALSO
savecrash(1M), crashconf(1M). crashutil(1M)
All times are GMT -4. The time now is 05:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy