Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of oliver.deakin@googlemail.com
 designates 64.233.182.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=googlemail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=f4eYOQewKrpC+3NoeKAqbL4R9LtQbIq/EbWFSfqkcLutQ+iby8afZPR0j1NAErd9GLS5rGjzx5UwRe3Ov4XCqqQ5R6NFjtgKymicI5iGYDi9zKse4bMG0T/9CeCpT9MyU9rDokNvySRL+ehS4BNfUnhuAbE0F108SuZSlCd4pIc=
Message-ID: <45520507.4060400@googlemail.com>
Date: Wed, 08 Nov 2006 16:25:43 +0000
From: Oliver Deakin <oliver.deakin@googlemail.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib] NLS exception messages arn't displayed correctly
References: <4550BF27.5020902@googlemail.com>
 <4550E6C9.9060503@gmail.com>	 <e29119980611072147s30e4a578ic0e8b3e247d905c2@mail.gmail.com>
	 <4551DD5B.20806@googlemail.com>
 <f944d83d0611080631j645d3209t637be29435a6b966@mail.gmail.com>
In-Reply-To: <f944d83d0611080631j645d3209t637be29435a6b966@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Alexey Varlamov wrote:
> 2006/11/8, Oliver Deakin <oliver.deakin@googlemail.com>:
>>
>> Evgueni Brevnov wrote:
>> > On 11/8/06, Tim Ellison <t.p.ellison@gmail.com> wrote:
>> >> Oliver Deakin wrote:
>> >> <SNIP!>
>> >> > 2) The bogus "FAILED to invoke JVM" message.
>> >> > Looks like this is coming from the launcher (Im running
>> >> > Harmony + IBM VME).
>> >> > It appears that this happens because in main_runJavaMain
>> >> > (in the launcher main.c) after we make the CallStaticVoidMethod()
>> >> > call to run main, we do the following:
>> >> >
>> >> > if ((*env)->ExceptionCheck (env))
>> >> >    {
>> >> >      if (rc == 0)
>> >> >        rc = 100;
>> >> >    }
>> >> >
>> >> > which causes a return code of 100 to be passed back to
>> >> > gpProtectedMain() via the invocation() function, where it is used
>> >> > in the following way:
>> >> >
>> >> > if (invocation(...))
>> >> >    {
>> >> >      hytty_printf (PORTLIB, "FAILED to invoke JVM.\n");
>> >> >      goto bail;
>> >> >    }
>> >> >
>> >> > I imagine this misleading message also appears with DRLVM?
>> >> > I'm not setup at the moment to test it.
>> >> > Is there a reason we set the return code to 100 if there's an
>> >> > unhandled exception?
>> >>
>> >> I'll leave that one for the person who changed the code ;-)
>> >
>> > Yes, I also observed such message when running with DRLVM. Actually,
>> > there is  the patch already which fixes the problem with the error
>> > code returned by the launcher to OS. Moreover this patch removes the
>> > misleading message as well. Look at
>> > http://issues.apache.org/jira/browse/HARMONY-2006 ....
>> > classlib_exit_code.patch
>>
>> Hi Evgueni,
>>
>> I have taken a look at the launcher patch for H2006, and for the most
>> part it looks good. The only thing that caught my eye was that you
>> have commented out the "FAILED to invoke JVM" error message completely.
>> This is still a useful message in some cases (where the VM fails to 
>> launch)
>> but should not be printed for cases where the VM has actually executed.
>> So perhaps we need a check here for the return value of invocation to
>> determine whether to print the message or not?
>
> Sounds reasonable - VM should not die silently. Please go for it.

Done in r472533.

Regards,
Oliver

>
> -- 
> Regards,
> Alexey
>
>>
>> Regards,
>> Oliver
>> >
>> > Thanks
>> > Evgueni
>> >
>> >>
>> >> Regards,
>> >> Tim
>> >>
>> >> --
>> >>
>> >> Tim Ellison (t.p.ellison@gmail.com)
>> >> IBM Java technology centre, UK.
>> >>
>> >
>>
>> -- 
>> Oliver Deakin
>> IBM United Kingdom Limited
>>
>>
>

-- 
Oliver Deakin
IBM United Kingdom Limited