Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!bacchus.pa.dec.com!deccrl!shlump.nac.dec.com!shodha.enet.dec.com!alan
From: alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.)
Newsgroups: comp.unix.ultrix
Subject: Re: DUMP: SIGSEGV()  ABORTING!
Summary: Not that bug?  How about this one...
Keywords: dump failing immediately.
Message-ID: <1763@shodha.enet.dec.com>
Date: 5 Oct 90 03:25:00 GMT
References: <1990Oct3.171146.4158@Neon.Stanford.EDU> <1753@shodha.enet.dec.com> <1990Oct5.001625.11355@Neon.Stanford.EDU>
Organization: Digital Equipment Corp. - Colorado Springs, CO.
Lines: 31

In article <1990Oct5.001625.11355@Neon.Stanford.EDU>, farhad@CS.Stanford.EDU (Farhad Shakeri) writes:
> In article <1753@shodha.enet.dec.com>, alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.) writes:
> |> In article <1990Oct3.171146.4158@Neon.Stanford.EDU>, farhad@CS.Stanford.EDU (Farhad Shakeri) writes:
> |> }
> |> } [ Dump fails with a segmentation fault. ]
> |> }
> |> 
> |> [ I suggest that it might a lack of the /etc/dumpdates file. ]
> 
> dump failed in all cases with or without 'u' .
>

	Not that bug, oh well.  Try this one.  Take a very close
	look at /etc/fstab.  Particularly the 2nd field of each
	line.  Are all the path names properly formed?  Do they
	all begin with '/'?  How about the rest of the file?  Any
	missing fields?  It seems that dump is very intolerent
	of a bad /etc/fstab.

	This too is a bug.  If it turns out to be this, then please
	submit an SPR on it.  While you're there you should also
	mention that a successful dump returns an exit status of
	one (1) instead of zero (0) like most programs.  I also
	consider this one a bug.  Maybe it will get fixed in the
	OSF/1 based system...
> -- 
>       /   Farhad Shakeri       E-Mail:                     /


-- 
Alan Rollow				alan@nabeth.enet.dec.com