00:00 <agentzh> what does "ship it hard" mean? sorry, i'm not a native speaker :P

00:00 <fche> silly frank joke

00:00 <fche> it means 'go for it'

00:00 <agentzh> oh, i see. thanks

14:37 <lindi-> is there some way to add exceptions to function("*") when probing user-space processes? usually there some some very common functions that are called often that I would like to exclude

14:58 <fche> lindi-, the closest thing would be the {a,b} type alternation syntax in the wildcard

14:58 <fche> or within the ("*") probe, add if (ppfunc() =~ "blacklist-regex") next;

15:00 <lindi-> fche: ok, I think I need to continue generating my stap scripts in python :)

17:04 <agentzh> for C stack backtrace output, gdb can also output the values of all the function frames' arguments and local vars if they are not optimized away, not just the top frame. is stap able to do the same thing? seems like stap can only inspect locals and args in the top frame of the stack?

17:05 <agentzh> i'm asking because sometimes we could only get the data structure entry points from earlier function frames in the current stack (like in the timer.profile probe handler).

17:06 <agentzh> lindi-: that is exactly what i'm doing for the same thing though i've been using perl to generate the stap script instead of python :)

17:18 <fche> agentzh, backtraces of such richness are indeed beyond what stap can attempt. A ton more debuginfo would have to be available to stap at runtime to make such computations.

17:45 <agentzh> fche: okay, that was also my guess. thanks for comfirming it!