Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site brl-tgr.ARPA Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!gwyn From: gwyn@brl-tgr.ARPA (Doug Gwyn) Newsgroups: net.lang.c Subject: Re: setjmp: read the manual Message-ID: <5320@brl-tgr.ARPA> Date: Mon, 15-Oct-84 20:45:11 EDT Article-I.D.: brl-tgr.5320 Posted: Mon Oct 15 20:45:11 1984 Date-Received: Wed, 17-Oct-84 19:34:43 EDT References: <1045@research.UUCP>, <1735@sun.uucp> Organization: Ballistics Research Lab Lines: 8 I am afraid I don't follow Sun's logic. All that is required is to unravel the call stack frames by following the back-pointers. The VAX built-in support for this stuff is not used on any UNIXes I am familiar with. When someone does a longjmp the odds are very good that it is not in the inside of a tight loop, so the extra time taken to unwind the stack frame to fix up clobbered registers should not be an efficiency issue, unless your call frames have a variable amount of information and no internal clue about how much.