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 translator/18701] New: systemtap can't find $return for sys_fadvise64_64 on rawhide


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

            Bug ID: 18701
           Summary: systemtap can't find $return for sys_fadvise64_64 on
                    rawhide
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com
                CC: mjw at redhat dot com
  Target Milestone: ---

On rawhide (4.2.0-0.rc2.git2.1.fc24.x86_64), the syscall testsuite fails
because the syscall tapset has an error in it. The error boils down to not
being able to find $return in kernel.function("sys_fadvise64_64").return:

====
# stap -ve 'probe kernel.function("sys_fadvise64_64").return { print($return)
}'
Pass 1: parsed user script and 109 library script(s) using
243680virt/44816res/7728shr/36980data kb, in 190usr/50sys/239real ms.
semantic error: unresolved target-symbol expression: identifier '$return' at
<input>:1:58
        source: probe kernel.function("sys_fadvise64_64").return {
print($return) }
                                                                         ^

Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s)
using 285420virt/87524res/8712shr/78720data kb, in 1380usr/120sys/1505real ms.
Pass 2: analysis failed.  [man error::pass2]
====

Here's the output of "eu-readelf -N --debug-dump=info
/usr/lib/debug/lib/modules/4.2.0-0.rc2.git2.1.fc24.x86_64/vmlinux" that
references "sys_fadvise64_64":

====
 [a4fac8]    subprogram
             external             (flag_present) Yes
             declaration          (flag_present) Yes
             linkage_name         (strp) "sys_fadvise64_64"
             name                 (strp) "sys_fadvise64_64"
             decl_file            (data1) 158
             decl_line            (data2) 461
====

There didn't seem to be any "formal parameter" entries for sys_fadvise64_64.

I did find one reference to [a4fac8]:

====
 [a4f2d3]      GNU_call_site
               low_pc               (addr) 0xffffffff810910f6
               abstract_origin      (ref4) [a4fac8]
 [a4f2e0]        GNU_call_site_parameter
                 location             (exprloc)
                  [   0] reg5
                 GNU_call_site_value  (exprloc)
                  [   0] GNU_entry_value:
                        [   0] reg5
 [a4f2e7]        GNU_call_site_parameter
                 location             (exprloc)
                  [   0] reg2
                 GNU_call_site_value  (exprloc)
                  [   0] GNU_entry_value:
                        [   0] reg9
====

Note that this has been going on for several rawhide kernels. Also note that
the nd_syscall (non-dwarf) testsuite passes fine.

-- 
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]