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 quit [Ping timeout: 240 seconds]
slowfranklin has joined #systemtap
slowfranklin has quit [Quit: slowfranklin]
orivej has joined #systemtap
Guest20286 is now known as vbernat
naveen2 has quit [Ping timeout: 255 seconds]
naveen2 has joined #systemtap
invano has quit [Ping timeout: 268 seconds]
invano has joined #systemtap
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #systemtap
orivej has quit [Ping timeout: 265 seconds]
zodbot has quit [*.net *.split]
agentzh has quit [*.net *.split]
ChanServ has quit [*.net *.split]
zodbot has joined #systemtap
ChanServ has joined #systemtap
orivej has joined #systemtap
orivej has quit [Ping timeout: 240 seconds]
brolley has left #systemtap [#systemtap]
agentzh has joined #systemtap
<agentzh>
fche: it's sad that stap's test scaffold cannot distinguish stdout and stderr output, it seems...
ChanServ has quit [*.net *.split]
<fche>
you mean dejagnu expect {} "
<fche>
?
ChanServ has joined #systemtap
<agentzh>
fche: i mean run_stap and run_stap3.
<agentzh>
seems like i should invoke tcl's primitives like exec and open myself?
<fche>
depends on what you'd like to do
<fche>
if you want to parse stdout / stderr yourself, you could spawn the subprocesses with explicit redirection to tmp files for stdout / stderr