harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HARMONY-5683) [drlvm][signals] Crash handler often can't print stack on Linux
Date Wed, 02 Apr 2008 18:09:24 GMT

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

Gregory Shimansky reassigned HARMONY-5683:

    Assignee: Gregory Shimansky

> [drlvm][signals] Crash handler often can't print stack on Linux
> ---------------------------------------------------------------
>                 Key: HARMONY-5683
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5683
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Linux
>            Reporter: Ilya Berezhniuk
>            Assignee: Gregory Shimansky
>            Priority: Minor
>         Attachments: H-5683.patch
> I've found that crash handler often prints only the first frame in stack dump.
> Investigation showed that stack range fails in unwind heuristics.
> A cause was also found: when VM maps unmapped stack area, it maps it with another access
flags (rw, default stack access is rwx).
> After that pthread_attr_getstack() returns only stack area mapped with default attributes
(before calling mmap() from VM).
> When crash occurs with SP value out of this small stack area mapped by default, unwind
heuristics fails to unwind frame.
> Suggested patch adds PROT_EXEC flag for mapping stack to match default flags.
> The patch also adds special processing for described situation with SP to crash handler;
the area starting the page containing current SP is added to stack area obtained through pthread_attr_getstack().

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

View raw message