From owner-freebsd-hackers Mon Jul 19 8:38:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 96D9114A12 for ; Mon, 19 Jul 1999 08:38:49 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA09792; Mon, 19 Jul 1999 11:46:22 -0400 (EDT) Date: Mon, 19 Jul 1999 11:46:20 -0400 (EDT) From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: Determining the return address In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 Jul 1999, Dag-Erling Smorgrav wrote: > Alfred Perlstein writes: > > On 18 Jul 1999, Dag-Erling Smorgrav wrote: > > > Hmm, I ended up using a global variable which I increment at the > > > beginning of the signal handler, and decrement at the end. > > As long as you make sure the code won't have multiple access > > that would work. > > Signal handlers having multiple accesses? When did you last see that > happen? erm, can't you point multiple signal handler entries to the same routine? can't you also make it so that signals aren't defered or blocked while another handler is executing so you may actually re-enter the handler before it's complete. specifically how you say you increment it, then decrement it, if you have multiple handlers where one can interupt another you can have the counter get jumbled. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message