emacs or csh problem?

[Paul Howell]

In article <27522 at netnews.upenn.edu>, hagan at scotty.dccs.upenn.edu (John
Dotts Hagan) writes:
|> 
|> 
|> You are running in /bin/csh like normal, and try and start an
application (like
|> the gnu emacs Digital distributes an unsupported subset):
|> ...
|> % emacs
|> Segmentation fault
|> % 
|> 
|> 
|> However, if you run another task:
|> 
|> % emacs
|> Segmentation fault
|> % emacs
|> Segmentation fault
|> % emacs
|> Segmentation fault
|> % emacs
|> Segmentation fault
|> % ls
|> fish
|> % emacs
|> <emacs starts up OK>
|>  ... 
|> The Segmentation fault occurs almost instantly, and core rarely dumps.  The
|> few times core has dumped, it is always a core dump of /bin/csh, not emacs.
|> Since the dumps are of the csh, and it fault happens so fast, I believe the
|> csh is having trouble starting the emacs task, rather than emacs causing the
|> problem.
|> ...
!> 
|> Again, if you are think you are experiencing these problems, please let me
|> know so I can let Digital know it is not a problem unique to my site.  Also,
|> if you know the problem, PLEASE LET ME KNOW - it's driving us crazy!!!!!!!!!
|> 
|> --Kid.

We had the same problem here with emacs giving a segmentation fault.  And only
after exec'ing something, would emacs work.  Our thoughts were that it was/is
a problem with csh.  sh didn't have the problem.

We're now running Ultrix 3.1d and haven't seen the problem again.  Not to say 
it's fixed, but I'm not an emacs user so I can only go by what others say.


---
Paul Howell
grue at caen.engin.umich.edu