Hi Dave,
Responses inline.
On 06/14/10 07:15 AM, Dave Miner wrote:
On 06/11/10 03:18 PM, Karen Tung wrote:
On 06/10/10 07:28 AM, Dave Miner wrote:
Karen, one more comment that I neglected to include in my first
response.
Rather than the DEBUG support described in section 12, have you
considered DTrace as the solution? The Python DTrace provider covers
many of the cases where I've seen debug-style statements used in the
past.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
Hi Dave,
I am not familiar with the Python Dtrace provider in Solaris. To answer
your question
above, I did a little research and some quick learning. Most of the
examples I saw
are tracing the entry and exit of functions. Tracing the functions and
seeing which ones
are called and when is certainly useful. Another thing that I found
useful is
displaying the value of some of the variables. For the engine's case, I
think
it would be useful to see what modules and checkpoints are
registered, and
what arguments they are registered with, or the normalized progress
value
the engine calculated. Those are the kind of things I plan to log
at the DEBUG level.
Those would, I think, be candidates for static probes, assuming that
there's a way to define static probes in Python. If not, then I agree
that it wouldn't meet those requirements.
Defining static probes in Python is not supporting yet.
During my research and learning, I also found that the Python Dtrace
provider
is only available for python 2.4. It is not available for Python 2.6
yet.
So, we won't be able to utilize it until it is ported to 2.6.
Have you inquired as to the plans to port it? Seems that the overall
move to 2.6 in Solaris was a bit incomplete if this work wasn't included.
I checked with John Levon, he said that the Python Dtrace provider works
with Python 2.6 too.
Based on these information, it appears that the engine can use Python
Dtrace provider
to trace the entry and exit of functions, but it can not be used for
tracking variables inside
functions. So, the engine implementation will use DEBUG log level to
print out
variables that's useful to monitor, and use Python Dtrace provider to
follow the flow
of when varies functions are called.
Thanks,
--Karen
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
