Memory fault in ql session

Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Memory fault in ql session
# 1  
Old 10-26-2007
Memory fault in ql session


Am getting memory fault when i start ql session in SCO unix server.
Can any one suggest the way to solve this issue.

Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

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

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. 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 ( to monitor the... (2 Replies)
Discussion started by: waseem
2 Replies

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

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

6. 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 (gcc version 3.2.3... (0 Replies)
Discussion started by: wsetchell
0 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. 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

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

10. UNIX for Dummies Questions & Answers

Memory Fault

I am using Unix OpenServer Release 5. When a run a application with user different to "Superuser" the application give me the following error: "Memory Fault - Core Dump". What's that mean? Thank you in advance. Roberto Veras. (1 Reply)
Discussion started by: robertoveras
1 Replies
Login or Register to Ask a Question
pfm_cleanup(3ncs)														 pfm_cleanup(3ncs)

       pfm_cleanup - establish a clean-up handler

       #include <idl/c/base.h>
       #include <idl/c/pfm.h>

       status_$t pfm_$cleanup(cleanup_record)
       pfm_$cleanup_rec *cleanup_record;

       cleanup_record	   A  record  of the context when is called.  A program should treat this as an opaque data structure and not try to alter
			   or copy its contents.  It is needed by and to restore the context of the calling process at the clean-up handler  entry

       The  routine  establishes a clean-up handler that is executed when a fault occurs.  A clean-up handler is a piece of code executed before a
       program exits when a signal is received by the process.	The clean-up handler begins where is called; the routine registers an entry  point
       with the system where program execution resumes when a fault occurs.  When a fault occurs, execution resumes after the most recent call to

       There  can  be  more  than one clean-up handler in a program.  Multiple clean-up handlers are executed consecutively on a last-in/first-out
       basis, starting with the most recently established handler and ending with the first clean-up  handler.	 The  system  provides	a  default
       clean-up  handler  established at program invocation.  The default clean-up handler is always called last, just before a program exits, and
       releases any system resources still held, before returning control to the process that invoked the program.

       When called to establish a clean-up handler, returns the status pfm_$cleanup_set to indicate the clean-up handler was  successfully  estab-
       lished.	 When the clean-up handler is entered in response to a fault signal, effectively returns the value of the fault that triggered the

       This section lists status codes for errors returned by this routine in

       pfm_$bad_rls_order  Attempted to release a clean-up handler out of order.

			   There is no pending clean-up handler.

       pfm_$cleanup_set    A clean-up handler was established successfully.

			   Attempted to use pfm_$cleanup_set as a signal.

			   Passed an invalid clean-up record to a routine.

       pfm_$no_space	   Cannot allocate storage for a clean-up handler.  Clean-up handler code runs with asynchronous faults  inhibited.   When
			   returns  something  other  than  pfm_$cleanup_set indicating that a fault has occurred, there are four possible ways to
			   leave the clean-up code:

			   o	  The program can call to start the next clean-up handler with a different fault signal.

			   o	  The program can call to start the next clean-up handler with the same fault signal.

			   o	  The program can continue with the code following the clean-up handler.  It should  generally	call  to  reenable
				  asynchronous	faults.   Execution  continues from the end of the clean-up handler code; it does not resume where
				  the fault signal was received.

			   o	  The program can reestablish the handler by calling before proceeding.

See Also
       intro(3ncs), pfm_signal(3ncs)