fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
orivej has joined #systemtap
_whitelogger has joined #systemtap
slowfranklin has joined #systemtap
<agentzh> fche: i found some regressions in my stap hanging patch. will submit a V2 patch for review. sorry about that.
invano has quit [Quit: Leaving]
invano_ has quit [Quit: leaving]
invano has joined #systemtap
mjw has joined #systemtap
brolley has joined #systemtap
wcohen has quit [Remote host closed the connection]
wcohen has joined #systemtap
gila has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
slowfranklin has quit [Quit: slowfranklin]
orivej has quit [Ping timeout: 252 seconds]
orivej has joined #systemtap
orivej has quit [Ping timeout: 252 seconds]
gila has joined #systemtap
brolley has left #systemtap [#systemtap]
<agentzh> fche: v2 patch is just sent: https://sourceware.org/ml/systemtap/2018-q4/msg00117.html
<agentzh> fixed the fd variable typo; also make sure the stderr/stdout devices are left blocking right before exiting; and fixed the first 2 Ctrl-C wouldn't work regression.
<agentzh> please let me know if it's good to commit. thanks!
<fche> hm, surprised at having to restore fcntl .... I thought fcntl flags were associated with the fd, not the file itself
<fche> i.e., other processes holding onto the same file with fd's wouldn't be affected
<fche> anyway it looks fine overall
<fche> go for it
gila has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
<agentzh> fche: yeah, i was surprised too. but certain env like vim seems to have persistent nonblocking effects which make subsequent stap runs fail...weird.
<agentzh> restarting a new shell session fixes that.
<agentzh> or making stap turning back to blocking mode.