Follow-up to [Bug translator/14596] New: probe module enhancement request

[Chaiken, Alison]

FChE responds:
Hm, so a drm.ko file was not even found apparently.
What does % strace stap .... 2>&1 | grep -i drm.ko    say?

Alison:
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.

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:

   stap: invalid option -- ' ' 

results with -L 'module("*").function("*")'.

Reversing the single and double quotes and trying again produces

   syntax error near unexpected token `('

as did no quotes at all.   Perhaps this is due to the stap version?

   [achaiken@sb-ubuntu-1204-64bit systemtap]$ stap --version
   Systemtap translator/driver (version 1.6/0.152 non-git sources)

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, and that I need to configure it to look in the right place, perhaps with the "-d" or "--sysenv" switch?

We're using Yocto to cross-compile, so perhaps not a lot of others have tried that particular use case yet?

Thanks again,
Alison Chaiken
Mentor Embedded Software Division