[Bug runtime/12566] New: usymbols.exp 64-bit test failing on ppc64

["dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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

           Summary: usymbols.exp 64-bit test failing on ppc64
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap@sourceware.org
        ReportedBy: dsmith@redhat.com


After fixing the testcase problem outlined here:

BZ639344 (usymbols.exp fails on ppc and s390x)
<https://bugzilla.redhat.com/show_bug.cgi?id=639344>

the usymbols.exp fails with a real problem on ppc64 (2.6.32-120.el6.s390x and
2.6.32.12-115.fc12.ppc64).

====
Snapshot: version 1.5 /0.152 commit release-1.4-143-gbd8504c + changes
GCC: 4.4.5 [gcc (GCC) 4.4.5 20110214 (Red Hat 4.4.5-6)]
Distro: Red Hat Enterprise Linux Server release 6.1 Beta (Santiago)

Running /root/src/testsuite/systemtap.context/usymbols.exp ...
FAIL: usymbols -m64
PASS: usymbols -m32

        === systemtap Summary ===

# of expected passes        1
# of unexpected failures    1
====

The 64-bit test is failing because the script outputs:

====
handler: 0x10010c48 (<unknown>)
handler: lib_handler (/root/ppc64/testsuite/libusymbols-m64.so)
====

Instead of something like:

====
handler: main_handler (/root/ppc64/testsuite/usymbols-m64)
handler: lib_handler (/root/ppc64/testsuite/libusymbols-m64.so)
====

>From looking at the test executable, 0x10010c48 is the correct address for
main_handler so systemtap should have all the information necessary to do the
lookup, but it somehow fails.

Note that this test completely passes on:

2.6.32-71.18.2.el6.x86_64
2.6.32-71.18.2.el6.i686
2.6.32-120.el6.s390x

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