This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Follow-up to [Bug translator/14596] New: probe module enhancement request
- From: "Frank Ch. Eigler" <fche at redhat dot com>
- To: "Chaiken, Alison" <Alison_Chaiken at mentor dot com>
- Cc: "systemtap at sourceware dot org" <systemtap at sourceware dot org>, "Baxter, Jim" <Jim_Baxter at mentor dot com>
- Date: Wed, 19 Jun 2013 14:19:57 -0400
- Subject: Re: Follow-up to [Bug translator/14596] New: probe module enhancement request
- References: <60BA5429A0E1584BA3633194F6F993B5027C77F2 at NA-MBX-03 dot mgc dot mentorg dot com> <60BA5429A0E1584BA3633194F6F993B5027F7D7B at NA-MBX-03 dot mgc dot mentorg dot com>
Hi -
> > What does % strace stap .... 2>&1 | grep -i drm.ko say?
> Nothing. I dumped the strace output into a file and searched over
> it, and there are no occurrences of "drm.ko". Note that drm.ko is
> not a particular problem; that module was picked at random. There
> is no module that works.
OK. Does the strace give a hint at where stap *is* looking for the
modules? There should be a bunch of stat / openat / getdents type
syscalls.
> FChE continues:
> What about % stap .... -L 'module("*").function("*")' ?
> I can't figure out how to invoke a command with nested quotes,
> either from CLI or from a script:
You could just run it directly as I typed it.
% stap <<<YOUR OTHER -r/-a/-B/etc. OPTIONS HERE>>> -L 'module("*").function("*")'
> [achaiken@sb-ubuntu-1204-64bit systemtap]$ stap --version
> Systemtap translator/driver (version 1.6/0.152 non-git sources)
(You may be able to build or get hold of a newer version;
that's two years old.)
> Presumably the most likely problem of the overall compilation
> failure is that stap doesn't know the path to search for the
> compiled kernel modules [...]
You're right. The question is how to trick that old version into
doing what you need.
- FChE