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 Marc.Abramowitz
Recipients Garen, Marc.Abramowitz, belopolsky, benjamin.peterson, danchr, dhduvall, dmalcolm, eric.snow, fche, glyph, hazmat, jbaker, jcea, jmcp, laca, lasizoillo, loewis, mjw, movement, neologix, pitrou, rhettinger, robert.kern, ronaldoussoren, scox, serverhorror, sirg3, techtonik, twleung, wsanchez
Date 2012-02-22.17:19:50
SpamBayes Score 6.8509034e-05
Marked as misclassified No
Message-id <>
My understanding of DTrace is extremely shallow, but I think there is a major difference in how USDT probes are created between Solaris and OS X. Whereas on Solaris one generates object code using the -G option of dtrace and then links it in with the application, it seems that on OS X, the header file that dtrace -h spits out already has the magic assembler voodoo in it and thus you don't link with anything extra for DTrace. If that's true, then we probably need Makefile ifdef stuff to make it work.

If someone can verify my theories, I might be inclined to take a stab at it.
Date User Action Args
2012-02-22 17:19:51Marc.Abramowitzsetrecipients: + Marc.Abramowitz, loewis, rhettinger, jcea, ronaldoussoren, belopolsky, pitrou, wsanchez, movement, techtonik, benjamin.peterson, serverhorror, glyph, laca, twleung, jbaker, robert.kern, sirg3, danchr, dhduvall, dmalcolm, mjw, Garen, neologix, lasizoillo, fche, hazmat, eric.snow, jmcp, scox
2012-02-22 17:19:51Marc.Abramowitzsetmessageid: <>
2012-02-22 17:19:51Marc.Abramowitzlinkissue13405 messages
2012-02-22 17:19:50Marc.Abramowitzcreate