13:48 <arjun> I just wrote a systemtap patch (changes to elaborate.cxx), configured, made, and installed (to /usr/local). I don't see my changes take effect when I run 'stap'.

13:48 <arjun> Anything I'm doing wrong?

13:50 <arjun> I'm trying to improve some of the warnings in Pass 2. Even the simplest change like altering the message printed for an existing warning doesn't show up with I run stap. I see the warning from *before* the change.

13:52 <arjun> Initially, I was trying this with 'make rpm'. Then realized that unless I commit my changes, `make rpm' doesn't pick up my changes. Then I committed my changes (and installed and ran the built rpms). Still no joy. Now I dropped the rpm thing and just installed to /usr/local. Still not seeing my change reflected.

13:52 <arjun> I figure I'm missing something basic that every systemtap developer knows/does. But I don't know what.

13:53 <arjun> csanting: ^ (just found you from the git logs)

13:55 <arjun> fche2: ^

14:00 <arjun> Aha! I found one thing that I did wrong.

14:16 <arjun> Solution: On my fedora, running 'sudo stap' uses packaged stap binary (while for non-root it doesn't). Specifying 'sudo /usr/local/bin/stap' solved it.

19:18 <drsmith> arjun: Yeah, having multiple version of systemtap installed on your system causes those kinds of problems. After hitting that sort of thing multiple times, I always make sure there is only one version on my systems.