harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Berezhniuk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5893) [drlvm][signal] stack trace is not available for failing asserts
Date Sun, 13 Jul 2008 23:13:31 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613214#action_12613214

Ilya Berezhniuk commented on HARMONY-5893:

Unfortunately, I can't reproduce the problem now.
On my WinXP/x86 assert() shows dialog box regardless of mode specified with _CrtSetReportMode.

In the near future I'll become (I hope) an owner of 64-bit processor - so I'll be able to
check the bug on Win/x86_64.

As I remember, assert() in MSVC library prepares approximate register context manually, so
I disabled stack printing for aborts - there is no guarantee that the context is prepared
I'll make some experiments, and if the context prepared is quite good, we can use it for stack

> [drlvm][signal] stack trace is not available for failing asserts
> ----------------------------------------------------------------
>                 Key: HARMONY-5893
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5893
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Alexey Varlamov
> There is quite annoying peculiarity of crash handler, it reports no stack trace in case
of failed assert "due to missing register info".
> Would be really nice to fix this.

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

View raw message