21:29 <gila> I have a work path lets say: /code/something/long/build/lib/libfoo is there a shortcut way to define that path? e.g probe ($shortcut).function("myfunc") { } -- im doing this from the command line e.g adhoc tracing so no script

21:30 <fche> maybe command line options?

21:30 <fche> stap -e 'probe process(@1).function("myfunc") { }' /path/to/proc

21:31 <gila> right but I dont want to type /path/to/proc all the time...

21:31 <fche> you can say @1 several times in the script - is that what you mean?

21:31 <fche> or how else would you like to specify that string?

21:32 <gila> I tried export shortcut -- but it does not take that

21:32 <gila> i.e export shortcut=/path/to/whatever

21:32 <fche> as in an environment variable?

21:32 <gila> yes

21:33 <fche> then stap -e "foo $shortcut ..." should work in that the shell will interpose the env var value

21:33 <fche> (note double quote)

21:34 <fche> stap -e 'probe process(@1).function("myfunc") { }' $shortcut ?

21:34 <fche> or, since single quotes are easier for stap scripts to be enclosed by

21:34 <gila> let me try :)

21:38 <gila> stap -L 'process(@1).function("*")' $short <--- that works

21:38 <gila> stap -L 'process($short).function("*")' <--- this does not

21:41 <fche> yeah, shells don't expand $short type expressions inside single-quoted strings

21:41 <fche> you could .... stap -L 'process("'$short'").function("*")' kind of thing, but it looks bad

21:43 <gila> Ah ok nice, well i got what i need :) thats great, thanks fche

21:43 <fche> np, enjoy