[Bug runtime/13350] New: dwarf unwinder _stp_valid_pc_addr() invalid for s390x

[Bug runtime/13350] New: dwarf unwinder _stp_valid_pc_addr() invalid for s390x

[mjw at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=13350

             Bug #: 13350
           Summary: dwarf unwinder _stp_valid_pc_addr() invalid for s390x
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap@sourceware.org
        ReportedBy: mjw@redhat.com
    Classification: Unclassified


runtime/stack-dwarf.c contains _stp_valid_pc_addr() which checks whether or not
a given address is valid as either a kernel or user address. The current
implementation just doesn't work for s390x.

To get a good implementation we need answers similar to:
http://sourceware.org/ml/systemtap/2011-q4/msg00064.html

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[Bug runtime/13350] dwarf unwinder _stp_valid_pc_addr() invalid for s390x

[dsmith at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=13350

David Smith <dsmith at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |dsmith at redhat dot com
         Resolution|---                         |FIXED

--- Comment #1 from David Smith <dsmith at redhat dot com> ---
Commit f493740, which is the fix for bug #21726, also fixes this issue. In
general, systemtap is more segment aware now (KERNEL_DS vs. USER_DS). That
commit replaces _stp_valid_pc_addr() with a call to _stp_lookup_bad_addr().

-- 
You are receiving this mail because:
You are the assignee for the bug.