From owner-freebsd-hackers  Wed Mar  6 13:45:41 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA28193
          for hackers-outgoing; Wed, 6 Mar 1996 13:45:41 -0800 (PST)
Received: from schizo.cdsnet.net ([204.118.244.32])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA28187
          for <hackers@freebsd.org>; Wed, 6 Mar 1996 13:45:37 -0800 (PST)
Received: (from mrcpu@localhost) by schizo.cdsnet.net (8.6.12/8.6.12) id NAA00220; Wed, 6 Mar 1996 13:46:43 -0800
Date: Wed, 6 Mar 1996 13:46:43 -0800 (PST)
From: Jaye Mathisen <mrcpu@cdsnet.net>
To: hackers@freebsd.org
Subject: clobbered by longjmp?
Message-ID: <Pine.BSF.3.91.960306134501.28959X-100000@schizo.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
Precedence: bulk



In tracking down why I'm getting alarm() sent to my process several times,
rather than just once, I fired up gcc -Wall, which reports that one of my 
arguments "might be clobbered by longjmp or vfork'.  

I am guessing that this means the argument maybe needs to be declared as 
volatile, but heck if I know.

Any tips?