fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
hpt has joined #systemtap
sscox has joined #systemtap
sscox has quit [Ping timeout: 240 seconds]
sscox has joined #systemtap
sscox has quit [Read error: Connection reset by peer]
wmealing has joined #systemtap
* wmealing
waves
<wmealing>
super strange request, is it possible to execute a userspace program when a probe condition is met.. i cant see how if it is
<wmealing>
maybe i can call the kernels exec
<wmealing>
tldr; i want to fire up gdb on execution of a process, have it attach to the process
<wmealing>
the environment is somewhat complex, and i want to generalize the debugging technique.
<fche>
wmealing, yeah done this sort of thing before
<wmealing>
not bad, i'm seriously considering changing my job title from kernel security
<wmealing>
to hardware security
<fche>
hahah
<fche>
spectre getting you down?
<wmealing>
speculative execution is the gift that keeps on giving
<fche>
man tapset::guru-signal and tapset::system btw
<wmealing>
thank you.
<wmealing>
fche: out of interest.. have you tried stap on the new windows beta builds that run the linux kernel ?
<fche>
hm, no
<fche>
they run genuine linux on a little vm now, right/
<wmealing>
it panics the system on that.. i'm not sure why.. reported it ot them.
<wmealing>
yep
<fche>
panics heheh
<fche>
betcha the vm doesn't perform breakpoint emulation properly
<wmealing>
yep
<wmealing>
i imagine its their shim layer thats dying, because i got a perfectly sane vmcore from the kernel
wcohen has quit [Remote host closed the connection]
<fche>
tried a perf probe of the same vicinity?
<wmealing>
i didn't get a lot of time to try things because it was on a roadshow.
sscox has joined #systemtap
<wmealing>
but the salesdude reckons it was 'super robust'
<wmealing>
'orly'
<fche>
heh
<fche>
we use perf-probe as a proof-of-kernel-bug when stap manages to trigger something funk
<fche>
funky
<wmealing>
i'll keep that in mind
<wmealing>
its an upstream kernel, so it newer than what i'm used to working on.
<wmealing>
and i'm pretty sure we already support hyper-V as a vm/hardware layer
<wmealing>
to be fair, i dont think that the sales dude would have thought that someone would start probing the kernel agressively.. and he also didnt know who i worked for.
<fche>
what were they selling?
<wmealing>
but one can't turn down an opportunity like that.
<wmealing>
Demo'ing the kernel on win10 server.
<wmealing>
hyperdome .. something like that
<wmealing>
some big cpu system
<wmealing>
superdome
<wmealing>
new release is x86, its pre-release.
<wmealing>
the older superdome, hyperdome stuff was not x86
<wmealing>
my eyes glazed over with the sales talk
<wmealing>
then they offered a shell on a slide.
<wmealing>
i could not resist.
wcohen has joined #systemtap
<fche>
well done :)
khaled has joined #systemtap
yogananth has joined #systemtap
orivej has quit [Ping timeout: 268 seconds]
yogananth has quit [Remote host closed the connection]
yogananth has joined #systemtap
hpt has quit [Ping timeout: 240 seconds]
mjw has joined #systemtap
sscox has quit [Ping timeout: 268 seconds]
wcohen has quit [Ping timeout: 272 seconds]
orivej has joined #systemtap
sscox has joined #systemtap
wcohen has joined #systemtap
tromey has joined #systemtap
sapatel_ has quit [Quit: Leaving]
sapatel_ has joined #systemtap
sapatel_ is now known as sapatel
khaled has quit [Remote host closed the connection]
khaled has joined #systemtap
khaled has quit [Client Quit]
khaled has joined #systemtap
sapatel has quit [Quit: Leaving]
sapatel has joined #systemtap
yogananth has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #systemtap
ChanServ has quit [shutting down]
ChanServ has joined #systemtap
khaled has quit [Remote host closed the connection]
sscox has quit [Ping timeout: 240 seconds]
mjw has quit [Quit: Leaving]
wcohen has quit [Ping timeout: 240 seconds]
tromey has quit [Quit: ERC (IRC client for Emacs 28.0.50)]