I compiled a few examples from the SAT manual and tried to run them as it
is proposed in the tutorial. I start tracelogger -n1 -d1 and then an
example program. The tracelogger keeps running until I kill it with Ctrl-C.
What am I doing wrong?
This was broken in 6.3 - the daemon modes and number of iterations
options became mutually exclusive. It is scheduled for the next 6.3
patch, however I can’t comment on when that will be.
Serge Yuschenko wrote:
I compiled a few examples from the SAT manual and tried to run them as it
is proposed in the tutorial. I start tracelogger -n1 -d1 and then an
example program. The tracelogger keeps running until I kill it with Ctrl-C.What am I doing wrong?
Thank you Colin.
Is there any other way to turn the logging on and off? Looks like entire
SAT tutorial is based on the ‘-n -d’ options.
The documentation also says that tracelogger comes with a source code. I
could not find it.
Colin Burgess wrote:
This was broken in 6.3 - the daemon modes and number of iterations
options became mutually exclusive. It is scheduled for the next 6.3
patch, however I can’t comment on when that will be.Serge Yuschenko wrote:
I compiled a few examples from the SAT manual and tried to run them as it
is proposed in the tutorial. I start tracelogger -n1 -d1 and then an
example program. The tracelogger keeps running until I kill it with Ctrl-C.What am I doing wrong?
\
I’m glad you asked this question - I was about to! I hope you get an
answer regarding the tracelogger source too: I asked about that a
month or so ago and have heard nothing since. If I ever do I’ll post
the answer here.