Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!sunic!EU.net!ieunet!news.ieunet.ie!jkh
From: jkh@whisker.hubbard.ie (Jordan Hubbard)
Newsgroups: comp.os.386bsd.questions
Subject: Re: FreeBSD: emacs: missing library!?
Date: 05 Jul 1994 01:00:29 GMT
Organization: Jordan Hubbard
Lines: 40
Message-ID: <JKH.94Jul5010029@whisker.hubbard.ie>
References: <2va3j1$5f0@agate.berkeley.edu> <2va64i$5d9@ohlone.kn.PacBell.COM>
NNTP-Posting-Host: whisker.hubbard.ie
In-reply-to: smui@news.kn.PacBell.COM's message of 4 Jul 1994 23:31:30 GMT
In article <2va64i$5d9@ohlone.kn.PacBell.COM> smui@news.kn.PacBell.COM (Sherman Mui) writes:
Anthony Monroe (tmonroe@soda.berkeley.edu) wrote:
: Funny...when I tried to install emacs on my machine (even though I'm not the
: biggest fan of it) I got the same message every time I tried to run it.
^^^^^^^^^^^^^^^^^
Why not!? :-)
: Well, I can't remember it exactly, but it amounted to "Segmentation fault --
: core dumped." And it would just put me back at the prompt. And this is
Doesn't that mean it tried to get some memory already taken?
Uhhhh. You guys are all WAY offbase! The `segmentation fault' is caused
when the program attempts an illegal memory access, not because it
tried to use memory already allocated to someone else! :-) [All processes
have their OWN address space]. An example:
jkh@whisker-> cat > foo.c
main()
{
char *foo = 0;
*foo = 10;
}
jkh@whisker-> cc foo.c -o foo
jkh@whisker-> ./foo
Segmentation fault (core dumped)
Make more sense?
So the emacs problem is not the result of trying to use `already
allocated memory' or `trying to use too much memory' (I run emacs + X
in 8MB all the time, for what it's worth), it's a bogus installation
of emacs! To put it more bluntly: When Antony attempted to install
emacs, he blew it somewhere..
Jordan
--
Jordan K. Hubbard FreeBSD core team Friend to mollusks