This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/19513] New: on rhel7 s390x, probing process.function("main").return causes the target to get an illegal instruction


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

            Bug ID: 19513
           Summary: on rhel7 s390x, probing
                    process.function("main").return causes the target to
                    get an illegal instruction
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com
  Target Milestone: ---

On RHEL 7.2 (3.10.0-327.el7.s390x), the global_var.exp testcase has several
failures:

====
Running ../../src/testsuite/systemtap.base/global_var.exp ...
PASS: global_var-m64
FAIL: global_var-m31
PASS: global_var-m64-O
FAIL: global_var-m31-O
PASS: global_var-m64-O2
FAIL: global_var-m31-O2
====

As you can see, they all relate to probing 31-bit executables. The problem
occurs when probing process.function("main").return. The test case prints a
global variable from that probe, but it appears really to just be the act of
probing itself:

====
# stap -e 'probe process.function("main").return { printf("main return\n") }'
-c ./global_var_main_m31
WARNING: Child process exited with signal 4 (Illegal instruction)
main return
WARNING: /usr/local/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]
====

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]