[no subject]

[Jonathan Rees <Rees@YALE.ARPA>]

    Date: Saturday, 4 June 1983  13:21-EDT
    From: David Miller <Miller>
    To:   carey, rees

    When I try running T on PTRANS (/usr/yale/bin/t) it comes back with:
    	Segmentation fault (core dumped)
    What's going on?

This probably means that PTRANS has run out of "swap space."  Berkeley
Unix maintains a special area of the disk called "swap space" which it
uses for paging user processes.  On PTRANS this area is very small; it
will be enlarged in thee near future.  A "segmentation fault" is one way
that T could die if Unix runs out of swap space.

Another way T could die, after startup, would be by running out of "swap
space" as it expands the heap or as it begins to GC; in this case,
however, you should get the T error message "Error: memory exhausted"
and a breakpoint.

Unix T users should probably set a small "coredumpsize" limit, unless
they know what they're doing.  This can be done by putting the following
command in one's ".login" or ".cshrc" (I don't really know which is
better, but it shouldn't matter for most people):

	limit coredumpsize 100K

This will prevent Unix from writing core dumps of T images, which can be
quite large and can take a very long time (uninterruptible) to write.