Re: why does setjmp return 1 after longjmp(buf,0)?

Article View: comp.std.c

Article #1706

#1706

From: Doug Gwyn
Date: Sun, 16 Sep 1990 00:03

9 lines
757 bytes

In article <6511@muffin.cme.nist.gov> libes@cme.nist.gov (Don Libes) writes:
>Was there any discussion about "fixing" this?

I don't recall any, because it not only reflected existing practice,
it also is obviously essential to prevent a longjmp from returning to
the wrong branch of the setjmp return path.

Every version of longjmp I can recall ever maintaining worked exactly
that way.

Technical Details

Message-ID: <13866@smoke.BRL.MIL>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!aplcen!haven!adm!smoke!gwyn

References: <6511@muffin.cme.nist.gov>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: why does setjmp return 1 after longjmp(buf,0)?
Message-ID: <13866@smoke.BRL.MIL>
Date: 16 Sep 90 00:03:52 GMT
References: <6511@muffin.cme.nist.gov>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 9

Reply to Parent Message