Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <9148516.1175789492787.JavaMail.jira@brutus>
Date: Thu, 5 Apr 2007 09:11:32 -0700 (PDT)
From: "Pavel Afremov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Updated: (HARMONY-1650) [drlvm][exception handling]
 enqueuing references, doing finalization, running finalizers can lose a
 risen exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HARMONY-1650?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Afremov updated HARMONY-1650:
-----------------------------------

    Attachment: Fix-exn_raised-assertion-during-finalization-start-up.patch

Updated patch to Fix exn_raised assertion during finalization start up.

Fix consist in:
=E2=80=A2 save exception before start java method in Objects_To_Finalize::r=
un_finalizers and
=E2=80=A2 restore it after java method.


> [drlvm][exception handling] enqueuing references, doing finalization, run=
ning finalizers can lose a risen exception
> -------------------------------------------------------------------------=
------------------------------------------
>
>                 Key: HARMONY-1650
>                 URL: https://issues.apache.org/jira/browse/HARMONY-1650
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Serguei Zapreyev
>         Assigned To: Gregory Shimansky
>            Priority: Minor
>         Attachments: a4.java, Fix-exn_raised-assertion-during-finalizatio=
n-start-up.patch, H1650.ex_impl.2.patch, H1650.ex_impl.3.patch, H1650.ex_im=
pl.patch, lin.log, testGetMeth.java, testGetMeth1.java, win.log
>
>
> Memory allocation within VM causes irregularly enqueuing references, doin=
g finalization, running=20
> finalizers. These processes lead to losing an exception risen within a ja=
va programm executed by VM.=20
> Please look at the following stack:
> =09harmonyvm.dll!exn_clear()  Line 113=09C++
>  =09harmonyvm.dll!Objects_To_Finalize::run_finalizers()  Line 343=09C++
>  =09harmonyvm.dll!vm_run_pending_finalizers()  Line 472=09C++
>  =09harmonyvm.dll!vm_hint_finalize()  Line 193=09C++
>  =09gc.dll!gc_alloc(unsigned int in_size=3D0x0000000c, unsigned int ah=3D=
0x013c1f40, void * thread_pointer=3D0x0102d1e8)  Line 243 + 0x8=09C++
> <<<...>>>
> or at the following:
>  =09vmcore.dll!exn_clear()  Line 106=09C++
>  =09vmcore.dll!References_To_Enqueue::enqueue_references()  Line 453 + 0x=
5=09C++
>  =09vmcore.dll!vm_enqueue_references()  Line 516=09C++
>  =09vmcore.dll!vm_hint_finalize()  Line 192=09C++
>  =09gc.dll!Garbage_Collector::check_hint_to_finalize()  Line 208 + 0xc=09=
C++
>  =09gc.dll!gc_alloc(unsigned int size=3D0x0000000c, unsigned int ah=3D0x0=
0d71b90, void * tp=3D0x003be070)  Line 961=09C++
> <<<...>>>
> So, this intricated enough bug leads to instability of VM's behaviour.
> I'm going to attach the fix of the issue.
> The detecting test will be attached as well.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.