This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jcea
Recipients Garen, belopolsky, chrismiles, danchr, dhduvall, dmalcolm, fche, glyph, hazmat, jbaker, jcea, jmcp, laca, lasizoillo, loewis, mjw, movement, neologix, pitrou, rhettinger, robert.kern, ronaldoussoren, serverhorror, sirg3, twleung, wsanchez
Date 2011-11-17.16:12:51
SpamBayes Score 8.832413e-07
Marked as misclassified No
Message-id <>
New changeset: 7c1b63f949e7.diff

Now I detect lacking of dtrace privileges, both in the global zone and in a non-global zone.

For that, I verify that the process can actually insert a C-entry point probe in a well known function: PyEval_EvalCode. This should work ALWAYS, even if the dtrace instrumentation provided by this fails miserably.

We have to remember if we change that function name, someday...
Date User Action Args
2011-11-17 16:12:52jceasetrecipients: + jcea, loewis, rhettinger, ronaldoussoren, belopolsky, pitrou, wsanchez, movement, serverhorror, glyph, laca, twleung, jbaker, robert.kern, sirg3, chrismiles, danchr, dhduvall, dmalcolm, mjw, Garen, neologix, lasizoillo, fche, hazmat, jmcp
2011-11-17 16:12:52jceasetmessageid: <>
2011-11-17 16:12:51jcealinkissue13405 messages
2011-11-17 16:12:51jceacreate