Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: 202.81.18.154 is neither permitted nor
 denied by domain of firepure@gmail.com)
Message-ID: <44DBE924.7060900@gmail.com>
Date: Fri, 11 Aug 2006 10:19:16 +0800
From: "Jimmy, Jing Lv" <firepure@gmail.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][instrument]Method to terminate VM.
References: <e66844de0608091952j5fbd0a6ey58c2b79a257bb854@mail.gmail.com>
In-Reply-To: <e66844de0608091952j5fbd0a6ey58c2b79a257bb854@mail.gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Leo Li wrote:
> Hi, all
>     During the implementaion of instrument, I encounter the choice about
> how to terminate the VM when some abnormal event occurs, for example, the
> expected jar file does not exist or the implementation class of
> Instrumentation cannot be found. The most simple and direct way is just to
> call exit(), and then the whole process will terminate. Hence OS will treat
> with all the release of resources. However, I propose to use FatalError of
> JNI instead, which notifies the VM to suicide, because it gives right to 
> the
> implementation of VM to take charge of its own funeral affairs, which might
> include, for example, logging the cause of its crash.
>    Any suggestion from VM guys?
>    Thanks :)
> 

Hi,

     I agree that use VM FatalError is better than system exit(). If no 
objections, I will make code that way.

-- 

Best Regards!

Jimmy, Jing Lv
China Software Development Lab, IBM

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org