Jeff
10-21-2009, 04:47 PM
In order to diagnose some problems, it will be necessary to capture
a Mobius trace log and send it to me for evaluation. This post describes
how that is done, the steps are different for Windows and Mac.
Trace Levels
There are several levels of logging available, by default only serious
errors are logged. To diagnose problems it is necessary to change the
logging level so normal status messages are logged instead of just
errors.
In the Global Preferences dialog there are two global parameters that
control the logging level: "Trace Print Level" and "Trace Debug
Level".
Trace Print Level controls the messages that are sent to the console.
On Mac the messages are sent to the system console that you can view
with the /Applications/Utilities/Console application. On Windows
console messages are only visible if you launched Mobius from
the command line instead of the start menu or an icon. Since it
is unusual to start Mobius from the command line you usually set
Trace Debug Level instead.
Trace Debug Level controls the messages that are sent to the "debug
output stream" when running under Windows. Since OS X doesn't
have the concept of a debug output stream this parameter is
treated the same as Trace Print Level. To view the debug output
stream you need to download an application. This is described
in more detail below.
Mac Trace Logging
Bring up the Configuration->Global Parameters Dialog and set Trace
Print Level to 2. Restart Mobius. Run the "Console" application
which is in the "Utilities" folder under the "Applications" folder.
Windows Trace Logging
Bring up the Configuration->Global Parameters Dialog and set Trace
Debug Level to 2. Restart Mobius. Run any debug stream viewer
application. The one I use most often is DBWIN32 which used
to be available here but the site was down the last time I tried it:
http://grantschenck.tripod.com/dbwinv2.htm
Another one is available from Microsoft:
http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
Using Trace
Once you have set the trace level and started the console application,
Record a quick loop to verify that you see messages in the console.
NOTE: There is a bug in 1.40 that will cause many messages of this
form to be logged.
0 0: 0 millis between interrupts
You can ignore these though it makes it difficult to see the
interesting messages.
You should see messages like this:
101 -5120: Function Record down
101 -5120: Loop: Add event Record(Record) 0
101 -5120: Loop: Set mode play
If you see trace messages, start using Mobius in the way you were
using it when the problem happened. As soon as the problem happens,
bring go to the console window, copy the contents and send them to me
in an email message. If the log is very long, it is better to save it
to a text file, then send the file as an email attachment.
My address is:
jeff@circularlabs.com
a Mobius trace log and send it to me for evaluation. This post describes
how that is done, the steps are different for Windows and Mac.
Trace Levels
There are several levels of logging available, by default only serious
errors are logged. To diagnose problems it is necessary to change the
logging level so normal status messages are logged instead of just
errors.
In the Global Preferences dialog there are two global parameters that
control the logging level: "Trace Print Level" and "Trace Debug
Level".
Trace Print Level controls the messages that are sent to the console.
On Mac the messages are sent to the system console that you can view
with the /Applications/Utilities/Console application. On Windows
console messages are only visible if you launched Mobius from
the command line instead of the start menu or an icon. Since it
is unusual to start Mobius from the command line you usually set
Trace Debug Level instead.
Trace Debug Level controls the messages that are sent to the "debug
output stream" when running under Windows. Since OS X doesn't
have the concept of a debug output stream this parameter is
treated the same as Trace Print Level. To view the debug output
stream you need to download an application. This is described
in more detail below.
Mac Trace Logging
Bring up the Configuration->Global Parameters Dialog and set Trace
Print Level to 2. Restart Mobius. Run the "Console" application
which is in the "Utilities" folder under the "Applications" folder.
Windows Trace Logging
Bring up the Configuration->Global Parameters Dialog and set Trace
Debug Level to 2. Restart Mobius. Run any debug stream viewer
application. The one I use most often is DBWIN32 which used
to be available here but the site was down the last time I tried it:
http://grantschenck.tripod.com/dbwinv2.htm
Another one is available from Microsoft:
http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
Using Trace
Once you have set the trace level and started the console application,
Record a quick loop to verify that you see messages in the console.
NOTE: There is a bug in 1.40 that will cause many messages of this
form to be logged.
0 0: 0 millis between interrupts
You can ignore these though it makes it difficult to see the
interesting messages.
You should see messages like this:
101 -5120: Function Record down
101 -5120: Loop: Add event Record(Record) 0
101 -5120: Loop: Set mode play
If you see trace messages, start using Mobius in the way you were
using it when the problem happened. As soon as the problem happens,
bring go to the console window, copy the contents and send them to me
in an email message. If the log is very long, it is better to save it
to a text file, then send the file as an email attachment.
My address is:
jeff@circularlabs.com