Your message dated Sat, 23 Feb 2019 01:11:26 +0100 with message-id <20190223001122.GA25370@orion> and subject line Re: Bug#789075: systemtap: Fails to find "kernel.trace" probe has caused the Debian Bug report #789075, regarding systemtap: Fails to find "kernel.trace" probe to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 789075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789075 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: systemtap Version: 2.6-0.2 Severity: normal I can't use "kernel.trace": # stap -vv -L 'kernel.trace("*")' Systemtap translator/driver (version 2.6/0.159, Debian version 2.6-0.2) Copyright (C) 2005-2014 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/stapmsrGIX" Session arch: x86_64 release: 3.16.0-4-amd64 Searched for library macro files: "/usr/share/systemtap/tapset/linux/*.stpm", found: 3, processed: 3 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: 70, processed: 70 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 106 library script(s) using 87600virt/32896res/5424shr/27948data kb, in 150usr/30sys/288real ms. Attempting to extract kernel debuginfo build ID from /lib/modules/3.16.0-4-amd64/build/vmlinux.id Attempting to extract kernel debuginfo build ID from /sys/kernel/notes semantic error: while resolving probe point: identifier 'kernel' at <input>:1:7 thrown from: elaborate.cxx:1062 source: probe kernel.trace("*") {} ^ semantic error: no match thrown from: elaborate.cxx:1025 Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s) using 88632virt/34936res/6388shr/28980data kb, in 10usr/80sys/143real ms. Tip: /usr/share/doc/systemtap/README.Debian should help you get started. Running rm -rf /tmp/stapmsrGIX Spawn waitpid result (0x0): 0 Removed temporary directory "/tmp/stapmsrGIX" I've installed linux-image, source, dbg and headers. Previously it was complaining it didn't find any System.map file, so I did this: cp /boot/System.map-3.16.0-4-amd64 /lib/modules/3.16.0-4-amd64/build/System.map -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemtap depends on: ii libavahi-client3 0.6.31-5 ii libavahi-common3 0.6.31-5 ii libc6 2.19-18 ii libdw1 0.159-4.2 ii libelf1 0.159-4.2 ii libgcc1 1:4.9.2-10 ii libnspr4 2:4.10.7-1 ii libnspr4-0d 2:4.10.7-1 ii libnss3 2:3.17.2-1.1 ii libsqlite3-0 3.8.7.1-1+deb8u1 ii libstdc++6 4.9.2-10 ii make 4.0-8.1 ii systemtap-common 2.6-0.2 ii systemtap-runtime 2.6-0.2 systemtap recommends no packages. Versions of packages systemtap suggests: pn systemtap-doc <none> pn vim-addon-manager <none> -- debconf-show failed
--- End Message ---
--- Begin Message ---Version: 2.8-1 On 17/06 07:29, Frank Ch. Eigler wrote: > This seems similar to this report: > > https://sourceware.org/ml/systemtap/2014-q4/msg00202.html > > ... which may be corrected by this upstream systemtap.git commit, > available in stap releases 2.7 and 2.8: > > commit b19a43768009076de3aea638922dfaebb687e3e9 > Author: Josh Stone <[email protected]> > Date: Thu Jan 8 14:47:20 2015 -0800 > > Use the kernel source symlink for tracepoints > > When the source symlink is different than the build symlink, as for > out-of-tree kernel builds and Debian linux-headers, then we should use > that path as a prefix for finding tracepoint headers. Indeed, `stap -vv -L 'kernel.trace("*")'` works fine now. Closing.
--- End Message ---
