Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!ucbvax!hidinger@cod.nosc.arpa@nosc.UUCP From: hidinger@cod.nosc.arpa@nosc.UUCP Newsgroups: mod.computers.apollo Subject: Submission for mod-computers-apollo Message-ID: <8612032140.AA05341@cod.ARPA> Date: Wed, 3-Dec-86 16:40:19 EST Article-I.D.: cod.8612032140.AA05341 Posted: Wed Dec 3 16:40:19 1986 Date-Received: Wed, 3-Dec-86 22:46:28 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 21 Approved: apollo@yale-comix.arpa Path: cod!hidinger From: hidinger@cod.UUCP (Ronald M. Hidinger) Newsgroups: mod.computers.apollo Subject: trapping a full disk Message-ID: <411@cod.UUCP> Date: 3 Dec 86 21:40:19 GMT Organization: Naval Ocean Systems Center, San Diego Lines: 12 I have a program which consumes massive amounts of dynamic memory. The inevitable problem is that the disk fills up and the program stops. It seems the new and rws_$alloc procedures don't detect that the disk is full. The fault occurs when the pointer is dereferenced. I have been able to trap this fault, but I haven't been able to do anything about it. When I dispose of some memory and return from the fault handler with the value pfm_$return_to_faulting_code the process dies without a clue as to what happened. Any suggestions about how to deal with this? sdcsvax!noscvax!hidinger