Path: csiph.com!x330-a1.tempe.blueboxinc.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date: Thu, 12 May 2011 20:33:02 -0500
Date: Thu, 12 May 2011 18:32:52 -0700
From: Patricia Shanahan <pats@acm.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
Newsgroups: comp.lang.java.programmer
Subject: Re: Java puzzler
References: <4db69c13-878f-4806-adb2-a3c5adb1c48c@glegroupsg2000goo.googlegroups.com> <qrGdnWE1mOKFHVfQnZ2dnUVZ_uKdnZ2d@earthlink.com> <alpine.DEB.2.00.1105112141410.27211@urchin.earth.li> <I6SdnROEzeMni1bQnZ2dnUVZ_sKdnZ2d@earthlink.com> <alpine.DEB.2.00.1105122029030.7602@urchin.earth.li> <-8mdnSRPEIdA21HQnZ2dnUVZ_j2dnZ2d@earthlink.com> <iqhhim$blg$4@speranza.aioe.org> <iqhjks$798$1@dont-email.me> <iqhv2p$at3$1@speranza.aioe.org> <iqhvso$a5a$1@dont-email.me> <iqi13v$fft$1@speranza.aioe.org>
In-Reply-To: <iqi13v$fft$1@speranza.aioe.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <I6CdnWoOvNfTF1HQnZ2dnUVZ_u6dnZ2d@earthlink.com>
Lines: 21
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 75.8.126.96
X-Trace: sv3-62OfEEcxeU6OFe4PSvfka0CCwQZbjaoCjei5bRDo8yu39khABn7EewEmOuEHRrnN7gyEbCjjj9Q9lmj!H7BnEaB4Nl3N5afX12qCAhf0g1vjMRHbp68oBuBFrbiY0V57vaQni4eA1wDA2QcJ8JBJt2tqCbG9!6NRPTXc5ZYosWGdr2W9q1pcf8s7YKRMdoW7t3QN5jAU=
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2382
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4035

On 5/12/2011 6:22 PM, Nancy 3 wrote:
> On 12/05/2011 9:01 PM, markspace wrote:
>> On 5/12/2011 5:47 PM, Nancy 3 wrote:
>>
>>> I'm sorry. I assumed you wanted an ArithmeticException or some other
>>> Java exception on overflow, rather than an application fault ala SIGSEGV
>>> that brings down the whole JVM. :)
>>
>> SIGSEGV can be trapped and redirected to the JVM to handle. It's a
>> hardware thing, not limited by any given implementation, *nix or
>> otherwise.
>
> Yes, but by then the stack has unrolled to wherever the handler is. The
> thread, at least, can't easily be restored to its previous state.

Last time I looked at signal handling, unrolling would only happen if
the signal handler did a long jump to a prior frame in the stack.

Patricia