#748697 systemtap integration across architectures and packages

Package:
systemtap
Source:
systemtap
Description:
instrumentation system for Linux
Submitter:
Matthias Klose
Date:
2025-08-17 17:47:54 UTC
Severity:
wishlist
Tags:
#748697#5
Date:
2014-05-19 19:00:10 UTC
From:
To:
systemtap support requires changes in many packages to enable systemtap support.
 I'm not sure if every maintainer of such a package is aware of this.  Please
could you track such a list of packages?   I think the best way would be a set
of bug reports filed with a systemtap user tag, a wiki page looks fine too if
updated on a regular basis.

Then it looks like you may need to provide the information which architectures
have systemtap support.  Doing that not in a central place will package
maintainers force to hard code this list of architectures.  Please provide such
a list of architectures.  An example for this might be from the java-common
package /usr/share/java/java_defaults.mk

#748697#12
Date:
2015-07-31 17:55:38 UTC
From:
To:
 ❦ 19 mai 2014 21:00 +0200, Matthias Klose <doko@debian.org> :

Maybe using sources.debian.net to find this list:

$ curl -s http://codesearch.debian.net/results/5d29ff30a4ba878c/packages.json | jq -r '.Packages[]'
tcl8.4
openjdk-7
zfs-fuse
libguestfs
zfsutils
kfreebsd-10
php5
glibc
apache2
nodejs
libreoffice
ust
systemtap
gjs
libeatmydata
qpid-cpp
haildb
icedove
ctfutils
libmemcached
openjdk-6
kfreebsd-kernel-headers
gearmand
openjdk-7-jre-dcevm
db5.3
freebsd-libs
xorg-server
pgtop
mozjs24
gcc-4.9
gnat-4.9
tcl8.5
fpc
erlang
mono
tcl8.6
db
gdb
wine-gecko-2.24
iceweasel
mozjs
hhvm
wine-gecko-2.21
mysql-proxy

However, the list is incomplete since the header inclusion doesn't have
to appear for a package to have support for systemtap. For examples,
lldpd is not in the list while it has support for it. It just uses
"dtrace" to generate the appropriate code. libvirt is another example
like that. We could search for packages having a ".d" file with
"provider" in it:

$ curl -s http://codesearch.debian.net/results/3afc484d5a9a1911/packages.json | jq -r '.Packages[]'
iceweasel
qtwebkit
mozjs24
icedove
wine-gecko-2.24
postgresql-9.4
tcl8.5
xorg-server
inn2
libvirt
db
julia
webkit2gtk
gjs
ruby2.2
inn
openjfx
mono
tcl8.4
perl
kfreebsd-10
libmemcached
php5
ruby2.1
db5.3
dnscrypt-proxy
pcp
mozjs
pike8.0
nodejs
cjs
xen
qtwebkit-opensource-src
ghc
moarvm
zfsutils
openjdk-7-jre-dcevm
mysql-proxy
nginx
glib2.0
apache2
erlang
wine-gecko-2.21
clisp
nsf
lldpd
memcached
tcl8.6
libuv
mariadb-10.0
systemtap

As for support, we could provide an arch all package depending on
systemtap-sdt-dev only on architectures where systemtap works (is that
authorized?). And a .mk with some appropriate variable that could be
used as a conditional.

Also, why is this bug marked as important? It's more a wishlist, right?
Downgrading.

#748697#19
Date:
2015-07-31 18:10:02 UTC
From:
To:
 ❦ 31 juillet 2015 19:55 +0200, Vincent Bernat <bernat@debian.org> :

Currently, systemtap-sdt-dev is arch any, so we could just add some
appropriate .mk to it. However, some packages specifically uses
arch-specific depends, so I suppose there is some reason for that. For
example, libvirt and php5.