Path: utzoo!attcan!uunet!wuarchive!cs.utexas.edu!rice!rice!sun-spots-request
From: dan@bbn.com (Dan Franklin)
Newsgroups: comp.sys.sun
Subject: Re: occam help (actually setjmp)
Keywords: Software
Message-ID: <1990Nov2.003137.11588@rice.edu>
Date: 2 Nov 90 00:20:00 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 7
Approved: Sun-Spots@rice.edu
Originator: spots@titan.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 356, message 5
X-Original-Date: Fri, 12 Oct 90 15:34:18 EDT
X-Refs:  Original: v9n351

Perhaps occam has its own runtime library of .o files that it loads with
the new libc from 4.1.  In that case, if those .o files were compiled
under Sun OS 3.X and any of them use setjmp(), they would cause weird
results, easily including a segmentation error and core dump, when used
with the 4.1 setjmp routine.  The reason is that the jmp_buf array used as
setjmp's argument is considerably larger under Sun OS 4.1 than 3.X (on
Sun-3s, at any rate).