ldv changed the topic of #strace to: https://strace.io | https://strace.io/logs/ | strace 5.2 is out | strace-devel@lists.strace.io for dev discussions
sscox has joined #strace
ldv has quit [*.net *.split]
ldv has joined #strace
mjw has quit [Quit: Leaving]
<mator> i should visit fosdem at least once... lets see ...
emachado has joined #strace
emachado has quit [Quit: Leaving]
<esyrd> mator: yes, 2020 sounds a nice year to have FOSDEM visited.
<esyrd> * sounds like
mjw has joined #strace
emachado has joined #strace
emachado has quit [Remote host closed the connection]
emachado has joined #strace
<pchaigno> Are the kernel constants in strace (e.g., BPF_* constants) kept in sync. with Linus's tree or with the latest release?
<pchaigno> Linus's tree has some new BPF constants and I'm not sure if I should add them now (but I don't have a git describe --contains tag) or wait for the first rc
<ldv> If there is no hurry I'd rather wait for an rc containing new features,
<ldv> but there is no rule for that, you don't have to wait for an rc.
<ldv> I'd like to cut v5.4, for this reason I temporarily switched travis and gitlab ci to use kernel headers from v5.4.
<pchaigno> <ldv> If there is no hurry I'd rather wait for an rc containing new features, // ok, I'll just need to update my script to compare against the last rc then :)
emachado has quit [Quit: Leaving]
sscox has quit [Ping timeout: 250 seconds]
sscox has joined #strace