You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Gregory Shimansky (JIRA)" <ji...@apache.org> on 2007/12/12 15:54:43 UTC
[jira] Created: (HARMONY-5297) [drlvm][crash handler] It would be
very helpful if crash handler printed VM memory map, command line arguments
and OS environment
[drlvm][crash handler] 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
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.
[jira] Commented: (HARMONY-5297) [drlvm][signals] It would be very
helpful if crash handler printed VM memory map, command line arguments and
OS environment
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553666 ]
Vladimir Beliaev commented on HARMONY-5297:
-------------------------------------------
Let's pick one category for all crash handler related issues, say "signals". Could someone fix the JIRA summary please?
> [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
>
> 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.
[jira] Resolved: (HARMONY-5297) [drlvm][signals] It would be very
helpful if crash handler printed VM memory map, command line arguments and
OS environment
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky resolved HARMONY-5297.
----------------------------------------
Resolution: Fixed
Patch is applied at 616840.
> [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, 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.
[jira] Commented: (HARMONY-5297) [drlvm][signals] It would be very
helpful if crash handler printed VM memory map, command line arguments and
OS environment
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HARMONY-5297) [drlvm][crash handler] It would be
very helpful if crash handler printed VM memory map, command line arguments
and OS environment
Posted by "Ilya Berezhniuk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550990 ]
Ilya Berezhniuk commented on HARMONY-5297:
------------------------------------------
Gregory, thanks for listing this.
I'm going to make some improvements in crash handling; printing modules mapping was in my initial plans.
Now I'll take other wishes into account.
I'm hoping to finish this by the end of December.
> [drlvm][crash handler] 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
>
> 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.
[jira] Commented: (HARMONY-5297) [drlvm][signals] It would be very
helpful if crash handler printed VM memory map, command line arguments and
OS environment
Posted by "Ilya Berezhniuk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564000#action_12564000 ]
Ilya Berezhniuk commented on HARMONY-5297:
------------------------------------------
Alexey,
thanks for your note!
I thought about this, but forgot to write it to my list of planned improvements :)
I'll update the patch soon.
> [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.
[jira] Updated: (HARMONY-5297) [drlvm][signals] It would be very
helpful if crash handler printed VM memory map, command line arguments and
OS environment
Posted by "Mikhail Markov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Markov updated HARMONY-5297:
------------------------------------
Summary: [drlvm][signals] It would be very helpful if crash handler printed VM memory map, command line arguments and OS environment (was: [drlvm][crash handler] It would be very helpful if crash handler printed VM memory map, command line arguments and OS environment)
> [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
>
> 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.
[jira] Updated: (HARMONY-5297) [drlvm][signals] It would be very
helpful if crash handler printed VM memory map, command line arguments and
OS environment
Posted by "Ilya Berezhniuk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Berezhniuk updated HARMONY-5297:
-------------------------------------
Attachment: H-5297.patch
Updated patch is attached.
> [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, 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.
[jira] Assigned: (HARMONY-5297) [drlvm][signals] It would be very
helpful if crash handler printed VM memory map, command line arguments and
OS environment
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky reassigned HARMONY-5297:
------------------------------------------
Assignee: Gregory Shimansky
> [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.
[jira] Updated: (HARMONY-5297) [drlvm][signals] It would be very
helpful if crash handler printed VM memory map, command line arguments and
OS environment
Posted by "Ilya Berezhniuk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Berezhniuk updated HARMONY-5297:
-------------------------------------
Attachment: H-5297.patch
Suggested patch contains requested features implemented.
Also the patch contains several additional improvements:
- corrected modules list filling for crash handling
- registers state is now printed under lock to prevent multiple threads from printing - for both GDB crash handler and common crash handler
- registers state printing is merged to be machine arch-dependent only
- 'cdecl' modifier in signals handling code is removed for x86_64
- GDB crash handling is corrected to get rid of parsing VM properties inside of crash
- port_executable_name rewritten to get rid of APR pools (for using in GDB crash handler)
- vm_find_method() is added to help with debugging release build in GDB (it's not called anywhere)
> [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
> 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.