You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Ilya Berezhniuk (JIRA)" <ji...@apache.org> on 2008/08/05 00:04:44 UTC
[jira] Commented: (HARMONY-5893) [drlvm][signal] stack trace is not
available for failing asserts
[ https://issues.apache.org/jira/browse/HARMONY-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619721#action_12619721 ]
Ilya Berezhniuk commented on HARMONY-5893:
------------------------------------------
I reproduced the problem on Win'x64.
Unfortunately, when I looked through CRT sources, I found that register context is prepared manually by CRT just before program termination.
I see no way to catch ABORT with register context - although CRT emulates 'signal' function and allows catching SIGABRT, it does not provide 'sigaction' which receives registers.
So the only solution I can see is preparing register context manually right in SIGABRT handler, like CRT does.
I'll try this way and report results.
> [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.