Author robert.kern
Recipients belopolsky, bretthoerner, chrismiles, danchr, jcea, laca, movement, rhettinger, robert.kern, ronaldoussoren, sirg3, skip.montanaro, twleung
Date 2009-04-23.23:43:32
SpamBayes Score 1.2067e-07
Marked as misclassified No
Message-id <1240530214.6.0.617631347766.issue4111@psf.upfronthosting.co.za>
In-reply-to
Content
Is there any interest in my expanding the list of probes? Ruby has quite
a few more than function-entry and function-return, to give some
examples of what is possible:

http://dev.joyent.com/projects/ruby-dtrace/wiki/Ruby+DTrace+probes+and+arguments

I think that adding probes that correspond to PyTrace_LINE and
PyTrace_EXCEPTION would be straightforward and worthwhile. PyTrace_C_*
may also be worthwhile, but you can probably accomplish similar things
with the normal pid probes if you know the C function names (although
something like printing the name of a raised exception will probably
require a dedicated probe).

Adding probes to replicate what the LLTRACE configuration option did,
but dynamically, might be interesting.
History
Date User Action Args
2009-04-23 23:43:35robert.kernsetrecipients: + robert.kern, skip.montanaro, rhettinger, jcea, ronaldoussoren, belopolsky, movement, bretthoerner, laca, twleung, sirg3, chrismiles, danchr
2009-04-23 23:43:34robert.kernsetmessageid: <1240530214.6.0.617631347766.issue4111@psf.upfronthosting.co.za>
2009-04-23 23:43:33robert.kernlinkissue4111 messages
2009-04-23 23:43:32robert.kerncreate