[Bug 1545324] Re: [wily][regression] syscall.clone not found

Brian Murray brian at ubuntu.com
Tue Feb 16 19:14:36 UTC 2016


Full error message:

bdmurray at clean-wily-amd64:~$ stap -vv -L 'nd_syscall.clone'
Systemtap translator/driver (version 2.8/0.163, Debian version 2.8-2ubuntu1 (wily))
Copyright (C) 2005-2015 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
enabled features: AVAHI LIBSQLITE3 NSS TR1_UNORDERED_MAP NLS
Created temporary directory "/tmp/stap1isGRS"
Session arch: x86_64 release: 4.2.0-18-generic
Kernel symbol table /lib/modules/4.2.0-18-generic/build/System.map unavailable, (No such file or directory)
Kernel symbol table /boot/System.map-4.2.0-18-generic unavailable, (Permission denied)
WARNING: Kernel function symbol table missing [man warning::symbols]
Searched for library macro files: "/usr/share/systemtap/tapset/linux/*.stpm", found: 5, processed: 5
Searched for library macro files: "/usr/share/systemtap/tapset/*.stpm", found: 5, processed: 5
Searched: "/usr/share/systemtap/tapset/linux/x86_64/*.stp", found: 3, processed: 3
Searched: "/usr/share/systemtap/tapset/linux/*.stp", found: 71, processed: 71
Searched: "/usr/share/systemtap/tapset/x86_64/*.stp", found: 1, processed: 1
Searched: "/usr/share/systemtap/tapset/*.stp", found: 24, processed: 24
Pass 1: parsed user script and 109 library script(s) using 104356virt/39576res/6640shr/32880data kb, in 110usr/20sys/175real ms.
semantic error: while resolving probe point: identifier 'kprobe' at /usr/share/systemtap/tapset/linux/nd_syscalls.stp:754:26
   thrown from: elaborate.cxx:1059
        source: probe nd_syscall.clone = kprobe.function("do_fork").call
                                         ^

semantic error: no match
   thrown from: elaborate.cxx:1022
semantic error: while resolving probe point: identifier 'nd_syscall' at <input>:1:7
   thrown from: elaborate.cxx:1059
        source: probe nd_syscall.clone {}
                      ^

semantic error: no match
   thrown from: elaborate.cxx:1022
Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s) using 105148virt/40608res/6896shr/33672data kb, in 10usr/0sys/4real ms.
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.
Running rm -rf /tmp/stap1isGRS
Spawn waitpid result (0x0): 0
Removed temporary directory "/tmp/stap1isGRS"


** Changed in: systemtap (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemtap in Ubuntu.
https://bugs.launchpad.net/bugs/1545324

Title:
  [wily][regression] syscall.clone not found

Status in systemtap package in Ubuntu:
  Confirmed

Bug description:
  Stap scripts involving "syscall.clone" probe point will fail
  It is due to a kernel change, which renamed "do_fork" to "_do_fork"
  and fails in both DWARF and dwarf-less situations.

  Upstream fixes:
  https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=4dde890792b69930e76e9667939bb08a80cdfb9c
  https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=e450540b4a2c0469a435e7b8e2a3e6285be76390

  Test:
  # stap -vv -L 'nd_syscall.clone'

  What should happen:
  command runs with no errors

  What happens:
  red lines with errors are printed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1545324/+subscriptions



More information about the foundations-bugs mailing list