fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
<fche>
if it survives a couple of rounds of that testing, ship it
<fche>
may it be an early christmas
<kerneltoast>
don't wanna just shippit and see what remains of the buildbots?
<fche>
the buildbots are still a bit sore about the week long red here and there
<fche>
I want to coddle them and comfort them this time
<kerneltoast>
they can take it
<kerneltoast>
fche, your command ain't working
<kerneltoast>
gimme better commands
<kerneltoast>
/bin/sh: systemtap.sum: No such file or directory
<fche>
hm, drop the .tcl one I think
<fche>
tell ya what, push your code to a branch, I'll also run some tests here
<kerneltoast>
okey
<kerneltoast>
gimme a branch name
<fche>
branch/name
<kerneltoast>
k
<irker170>
systemtap: sultan systemtap.git:sultan/bulkmode * release-4.4-23-g024d1fad3 / runtime/print_flush.c runtime/transport/relay_v2.c runtime/transport/transport.c runtime/transport/transport.h staprun/relay.c: always use per-cpu bulkmode relayfs files to communicate with userspace
<irker170>
systemtap: sultan systemtap.git:sultan/bulkmode * release-4.4-24-gfcd798b46 / tapset-timers.cxx: Revert "REVERTME: tapset-timers: work around on-the-fly deadlocks caused by mutex_trylock"
<kerneltoast>
fche, thar's yer branch
<fche>
ok
<fche>
btw that stp_print_*lock business needs to be duplicated lightly to the runtime/dyninst/* directory, else stap --runtime=dyninst won't build
<fche>
betcha kernel people such as yourself don't have the magic of dyninst-devel installed, thus your stap lacks this neat facility
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
khaled has quit [Quit: Konversation terminated!]
<fche>
kerneltoast, uprobes_onthefly.exp still struck dead by the code
<fche>
pity
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
irker170 has quit [Quit: transmission timeout]
<kerneltoast>
fche, oof
<kerneltoast>
well it's not the mutex_trylock at least
<kerneltoast>
we really gotta get some vmcores from the buildbots
<kerneltoast>
I'm running out of bugfixes to punt at you in the hopes of it fixing the buildbots
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
orivej has joined #systemtap
_whitelogger has joined #systemtap
mjw has quit [Quit: Leaving]
beauty2 has joined #systemtap
beauty1 has quit [Ping timeout: 272 seconds]
khaled has joined #systemtap
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #systemtap
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
<agentzh>
fche: well, we indeed let machines generate 99.99% of our stap scripts nowadays. manual stap scripting is just for testing and hacking on stap itself ;)
<agentzh>
it's not using neural networks yet, but maybe oneday we'll get there.
<agentzh>
currently the input is sql, the output is stap scripts...
<agentzh>
sometimes the input is C code or lua code. oh well.
<agentzh>
i meant to create some videos and blog posts to demonstrate all these soon. unforunately your stap mailing list hate youtube links. will find other ways...