*BSD News Article 15027


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!noc.near.net!uunet!mcsun!julienas!bull.bull.fr!clbull.frcl.bull.fr!antares!dage
From: dage@antares.Berkeley.EDU (Benoit.Dageville)
Newsgroups: comp.unix.bsd
Subject: longjmp with no longjmperror
Keywords: setjmp, longjmp
Message-ID: <1144@clbull.frcl.bull.fr>
Date: 23 Apr 93 18:03:15 GMT
Sender: news@clbull.frcl.bull.fr
Reply-To: dage@antares.Berkeley.EDU (Benoit.Dageville)
Lines: 15

I am currently implementing a thread package based on the setjmp/longjmp
functions. Under the bsd operating systems, an error is generated if the
contents of the jmp_buf is corrupted, or correspond to an environment
that has already returned (in this case longjmp calls the routine
longjmperror).  

Is there a way to turn off this functionnality ???. Otherwise it will be
not possible to create a thread package without reprograming the longjmp
function (in assembly of course). If there is no way to do that, has
someone write a version of longjmp without any test for the IBM rs6000
workstation (and others, mips for example ...)?

Thanks a lot for any reply (by email if possible)

Email : B.Dageville@frcl.bull.fr