fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
hkshaw has quit [Quit: Leaving.]
rth has quit [Quit: Leaving]
wcohen has quit [Remote host closed the connection]
wcohen has joined #systemtap
ego has quit [Ping timeout: 244 seconds]
hpt has joined #systemtap
cbzx has joined #systemtap
cbzx has quit [Quit: Konversation terminated!]
hkshaw has joined #systemtap
hpt has quit [Quit: Lost terminal]
hpt has joined #systemtap
hkshaw has quit [Quit: Leaving.]
ravi has joined #systemtap
ananth has joined #systemtap
Humble has quit [Ping timeout: 244 seconds]
ton31337_ is now known as ton31337
ph7 has joined #systemtap
naveen1 has joined #systemtap
hkshaw has joined #systemtap
Humble has joined #systemtap
nkambo has joined #systemtap
sorenson has quit [Ping timeout: 260 seconds]
Humble has quit [Ping timeout: 272 seconds]
lukas` has joined #systemtap
ph7 has quit [Quit: Leaving.]
sorenson has joined #systemtap
nkambo has quit [Read error: Connection reset by peer]
ph7 has joined #systemtap
Humble has joined #systemtap
hpt has quit [Quit: leaving]
hpt has joined #systemtap
hpt has quit [Quit: leaving]
ananth has quit [Quit: Leaving]
ananth has joined #systemtap
lukas` has quit [Remote host closed the connection]
<vincent->
But at the bottom of that document it says the following: "The host system must be the same architecture and running the same distribution of Linux as the target system in order for the built instrumentation module to work. "
<vincent->
What I want to to cross-compile the instrumentation module for a different target architecture. Let's say, the host arch is x86 and the target arch is mips.
<vincent->
Is that impossible to do?
<vincent->
I was thinking on building systemtap for the host architecture, so I can run the stap binary on the host, and then use it to cross-compile the instrumentation module for the target architecture.
ananth has quit [Quit: Leaving]
ph7 has joined #systemtap
naveen2 has quit [Quit: Leaving.]
srikar_away is now known as srikar
ph7 has quit [Quit: Leaving.]
ph7 has joined #systemtap
mbenitez has joined #systemtap
ph7 has quit [Quit: Leaving.]
<fche>
vincent-, this sort of thing can work
<fche>
see the [man stap] page section on -a ARCH
ph7 has joined #systemtap
ravi has quit [Remote host closed the connection]
wcohen has quit [Remote host closed the connection]
<irker741>
systemtap: csanting systemtap.git:refs/heads/master * release-3.0-99-g73ec640 / testsuite/systemtap.base/set_user.c testsuite/systemtap.base/set_user.stp: PR11637: Updated probe point for test case http://tinyurl.com/zwy8aka
<irker741>
systemtap: dsmith systemtap.git:refs/heads/master * release-3.0-124-gcb71bac / tapset/linux/nd_syscalls.stp tapset/linux/syscalls.stp testsuite/systemtap.syscall/fanotify.c: Make some small improvements to [nd_]syscall.fanotify_mark for RHEL7. http://tinyurl.com/jx63jnt
jdetter_ has joined #systemtap
ph7 has quit [Quit: Leaving.]
<jistone>
jdetter_, welcome
* jistone
== github @cuviper, fyi
<jdetter_>
thanks! Yeah, I think system tap looks really useful
<jdetter_>
It's a red hat project too right?
<fche>
jdetter_, hi
<jistone>
it's an open project, but yes, red hat does most of the development
<fche>
jdetter_, rh people have been its most regular contributors, but there are plenty of non-rh'ers too
<jdetter_>
oh sweet
<jdetter_>
what's the URL for git cloning?
<fche>
git://sourceware.org/git/systemtap.git is one
<jistone>
jdetter_, it's directly available on fedora and rhel too
hkshaw has quit [Quit: Leaving.]
<jistone>
a lot of the others too, but we're the most diligent about keeping up to date :)
<jdetter_>
that's good! :)
mbenitez has quit [Quit: To office]
srikar is now known as srikar_away
brolley|lunch is now known as brolley
<jdetter_>
Is it easiest to just run stap as root?
<fche>
most common uses of stap are for system-wide or kernel introspection, so those do require root (or equivalent)
<jdetter_>
on fedora do I just add myself to stapusr?
<jistone>
FYI, debuginfo isn't always needed. e.g. the "syscall.*" probes use debuginfo, but we've also aliased "nd_syscall.*" to make do without
<jdetter__>
ok, that's what it was complaining about was trying to do a system call probe without the debug info, installing the debug info fixed it for me :)
<jistone>
yeah, generally speaking you'll have a lot more available *with* debuginfo, so it's good to have
<jdetter__>
Ok great, thanks again, I'll probably have more questions in a bit :)
hpt has joined #systemtap
jdetter__ has quit [Quit: Leaving]
jdetter__ has joined #systemtap
jdetter__ has quit [Client Quit]
detter has joined #systemtap
<detter>
Ok, I'm using detter from now on :)
<jistone>
imposter!
<detter>
lol
franchesca has joined #systemtap
franchesca has quit [Remote host closed the connection]