fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
sscox has joined #systemtap
_whitelogger has joined #systemtap
irker960 has quit [Quit: transmission timeout]
orivej has joined #systemtap
yogananth has joined #systemtap
mjw has joined #systemtap
yogananth_ has joined #systemtap
yogananth has quit [Ping timeout: 276 seconds]
gromero_ has joined #systemtap
gromero has quit [Ping timeout: 276 seconds]
gromero_ is now known as gromero
tromey has joined #systemtap
khaled has joined #systemtap
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #systemtap
khaled has quit [Remote host closed the connection]
khaled has joined #systemtap
orivej has quit [Ping timeout: 245 seconds]
mjw has quit [Quit: Leaving]
orivej has joined #systemtap
mjw has joined #systemtap
sscox has quit [Ping timeout: 265 seconds]
mjw has quit [Quit: Leaving]
sscox has joined #systemtap
mjw has joined #systemtap
orivej has quit [Ping timeout: 276 seconds]
khaled has quit [Quit: Konversation terminated!]
agentzh has joined #systemtap
tromey has quit [Quit: ERC (IRC client for Emacs 26.1)]
mjw has quit [Quit: Leaving]
<agentzh> fche: it seems like stap does not bother using .debug files for userland stack unwinding? it just uses the elf sections .eh_frame and .eh_frame_hdr for that?
<fche> it can use .debug_frame if .eh_frame is not there
<fche> usually the binaries have one or the other, not both
<agentzh> ok, i see. thanks
<agentzh> fche: i wonder if it is required to use exactly the same version of gcc to build the stap kernel module as the one used to build the current running kernel.
<agentzh> or just using the same major series of gcc is fine.
<agentzh> like gcc 4.8.x or 5.x.
<fche> agentzh, generally it should be the same compiler, because the kernel configuration & header machinery sometimes does compiler version sensitive changes to structs etc., which break the abi
<fche> same rules as for building any out-of-tree module
<agentzh> yeah, i used to run into such ABI breakage in the past, hence the question.
<agentzh> wondering if the same gcc series wouldn't break that.
<agentzh> otherwise installing different versions of gcc for a lot of machines running stap is painful.
<agentzh> hopefully we can do some sort of "cross-compilation" here.
<agentzh> like stap -r DIR.
<fche> there is stap -B FOO_ to prefix compiler tools with something
<agentzh> yeah, that would be useful.
<agentzh> at least do not have to uninstall the default gcc.
<agentzh> but still we'll have to install a lot of different versions of gcc.
<agentzh> if we could just always use the latest version of gcc of the same series in a single distro, then it would be great.
<fche> run a stap compile server per distro
<fche> hm
<fche> we had earlier worked on a stap multi-compile-server prototype, whereby a single instance of stap-serverd would be able to spin up a docker buildroot for any arbitrary target os version, and run the build inside that
<fche> didn't quite finish it tho
<fche> you can see it in the source tree, httpd/ subdirectory