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, danchr, dhduvall, dmalcolm, fche, glyph, hazmat, jbaker, jcea, jmcp, laca, lasizoillo, loewis, mjw, movement, neologix, pitrou, rhettinger, robert.kern, ronaldoussoren, serverhorror, sirg3, techtonik, twleung, wsanchez
Date 2011-12-01.08:20:21
SpamBayes Score 6.5767847e-10
Marked as misclassified No
Message-id <>
The stack walker helper now supports unicode too. This was quite difficult!.

The patch is functionally complete.

Current patch is pretty final. It was easy and painless EXCEPT the stackhelper, because the "idea" of "PyCompactUnicodeObject" that GCC and DTRACE have are different. Current code includes a couple of "magic numbers". This can be fragile. But if it breaks, the only missing functionality would be the augmented stack dump. No crashed, because DTRACE probes are safe (for the program being monitored).

I guess the best idea would be to generate a ".h" at compile time, with the right magic constants.

I have tried to create global variables and import them from the stackhelper. That works... unless you use the "-c" DTrace argument. I guess I am hitting some bug in DTrace.

Pending: performance analysis. The performance hit should be very small.

Please, do a preliminar review.
Date User Action Args
2011-12-01 08:20:23jceasetrecipients: + jcea, loewis, rhettinger, ronaldoussoren, belopolsky, pitrou, wsanchez, movement, techtonik, serverhorror, glyph, laca, twleung, jbaker, robert.kern, sirg3, danchr, dhduvall, dmalcolm, mjw, Garen, neologix, lasizoillo, fche, hazmat, jmcp
2011-12-01 08:20:22jceasetmessageid: <>
2011-12-01 08:20:22jcealinkissue13405 messages
2011-12-01 08:20:21jceacreate