Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Nancy 3 Newsgroups: comp.lang.java.programmer Subject: Re: Java puzzler Date: Thu, 12 May 2011 21:22:08 -0400 Organization: N3 Solutions Inc. Lines: 12 Message-ID: References: <4db69c13-878f-4806-adb2-a3c5adb1c48c@glegroupsg2000goo.googlegroups.com> <-8mdnSRPEIdA21HQnZ2dnUVZ_j2dnZ2d@earthlink.com> NNTP-Posting-Host: taZaw1fZzaqFzuo6ews1KQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Forte Agent 2.0/32.652 X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4033 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.