Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <1729253824.1206699748426.JavaMail.jira@brutus>
Date: Fri, 28 Mar 2008 03:22:28 -0700 (PDT)
From: "Gregory Shimansky (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Assigned: (HARMONY-5656) [drlvm][port][signals] VM does not
 show assertion dialog on failed asserts
In-Reply-To: <1093140136.1206555445972.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HARMONY-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky reassigned HARMONY-5656:
------------------------------------------

    Assignee: Gregory Shimansky

> [drlvm][port][signals] VM does not show assertion dialog on failed asserts
> --------------------------------------------------------------------------
>
>                 Key: HARMONY-5656
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5656
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Windows
>            Reporter: Ilya Berezhniuk
>            Assignee: Gregory Shimansky
>         Attachments: assert_patch_03_2.patch
>
>
> When an assertion fired, VM does not show assertion dialog on Windows regardless of "vm.assert_dialog" property.
> The only case when assertion is displayed in a dialog is when crash handler is not initialized yet.
> The problem appears because in current crash handler design all CRT events are set up in crash handler initialization to print comsole message and do not display a dialog.
> The sceme supposed to re-enable CRT event setting in VEH. The problem with assert() is that the signal is caught neither in VEH nor in CRT handler.
> I can see 2 approaches to fix the problem:
> 1) Change CRT settings immediately when crash handler output flags are changed. This method introduces additional platform dependency and thus does not look good for me, but it shoul work stably.
> 2) SIGABRT handler can be registered on Windows, but Unix-like signals handling looks ugly in Windows environment.
> I'm going to try both methods, and provide a patch for working one.

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