Message158867
| Author |
fche |
| Recipients |
Garen, Marc.Abramowitz, belopolsky, benjamin.peterson, danchr, dhduvall, dmalcolm, eric.snow, fche, glyph, hazmat, jbaker, jcea, jmcp, laca, larry, lasizoillo, loewis, mjw, movement, neologix, pitrou, rhettinger, robert.kern, ronaldoussoren, scox, serverhorror, sirg3, twleung, wsanchez |
| Date |
2012年04月20日.18:21:41 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<20120420182137.GM18217@elastic.org> |
| In-reply-to |
<1334945372.71.0.198026631395.issue13405@psf.upfronthosting.co.za> |
| Content |
> Stan, anybody working in SystemTap support, could you possibly
> create a new issue in the tracker to track specifically stap
> support?. You can depend on this bug, and coordinate effort. Clone
> my repository and use it as base.
I believe the only remotely-systemtap-specific stuff we suggested
would be useful would be the addition of that PyEval_GetFrame() value
as an extra argument for function entry/exit sdt.h calls.
I believe your patch already apprx. works against systemtap (and in
fact many dtrace idiosyncracies like asm("nop") are unnecessary here),
except for the inclusion of the /usr/bin/dtrace -G-generated header
file, as mentioned in <http://bugs.python.org/issue13405#msg149054>.
Do you think it is necessary to track that in a separate bug?
- FChE |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年04月20日 18:21:42 | fche | set | recipients:
+ fche, loewis, rhettinger, jcea, ronaldoussoren, belopolsky, pitrou, wsanchez, movement, larry, benjamin.peterson, serverhorror, glyph, laca, twleung, jbaker, robert.kern, sirg3, danchr, dhduvall, dmalcolm, mjw, Garen, neologix, lasizoillo, hazmat, eric.snow, jmcp, scox, Marc.Abramowitz |
| 2012年04月20日 18:21:41 | fche | link | issue13405 messages |
| 2012年04月20日 18:21:41 | fche | create |
|