Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!shelby!neon!CS.Stanford.EDU!farhad
From: farhad@CS.Stanford.EDU (Farhad Shakeri)
Newsgroups: comp.unix.ultrix
Subject: Re: DUMP: SIGSEGV()  ABORTING!
Keywords: dump failing immediately.
Message-ID: <1990Oct5.004134.14192@Neon.Stanford.EDU>
Date: 5 Oct 90 00:41:34 GMT
References: <1990Oct3.171146.4158@Neon.Stanford.EDU> <14862@cbmvax.commodore.com>
Sender: news@Neon.Stanford.EDU (USENET News System)
Reply-To: farhad@CS.Stanford.EDU (Farhad Shakeri)
Organization: Computer Science Department, Stanford University
Lines: 23

In article <14862@cbmvax.commodore.com>, grr@cbmvax.commodore.com (George Robbins) writes:
|> In article <1990Oct3.171146.4158@Neon.Stanford.EDU> farhad@CS.Stanford.EDU (Farhad Shakeri) writes:
|> 
|> When I've seen this kind of problem, it has been due to a copy of the
|> image in the swap area getting corrupted.  If you reboot the machine,
|> and then try the dump again immediately, do you get the same problem?

YES!  I have done everything I can think of.  fsck, power on/off
no errors in errlog file.  checked the dumpdates file...

|> ...
|> > Also  can this be a hardware problem?
|> 
|> Could be...
|> 
|> -- 
|> George Robbins - 
-- 
       +----------------------------------------------------+
      /   Farhad Shakeri       E-Mail:                     /
     /  Stanford University    farhad@Tehran.Stanford.EDU /
    / Computer Science Dept.                             /
   +----------------------------------------------------+