You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2008/01/30 12:03:34 UTC

[jira] Commented: (HARMONY-5297) [drlvm][signals] It would be very helpful if crash handler printed VM memory map, command line arguments and OS environment

    [ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563973#action_12563973 ] 

Alexey Varlamov commented on HARMONY-5297:
------------------------------------------

Another possible improvement, print names of generated stubs in stack trace of crash dump:
stack_dump.cpp: fprintf(stderr, "%3d: 0x%"W_PI_FMT"  <Generated stub>\n",
AFAIK this info is available for free, you just need to add it to print.

> [drlvm][signals] It would be very helpful if crash handler printed VM memory map, command line arguments and OS environment
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-5297
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5297
>             Project: Harmony
>          Issue Type: Wish
>          Components: DRLVM
>         Environment: All
>            Reporter: Gregory Shimansky
>            Assignee: Gregory Shimansky
>         Attachments: H-5297.patch
>
>
> Often when VM crashes, especially in CC batch runs it isn't possible to recognize how VM was launched and in which environment. Keeping command line arguments used for JN_CreateJavaVM and then printing them at the crash point would be really helpful.
> Also additional information like OS environment and modules mapping would be helpful too.

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