New submission from Frank Ch. Eigler <f...@elastic.org>:
Similar to https://bugs.python.org/issue31574, it would be useful the the
interpreter allowed a tracing tool to hook the PyCFunction_Call() site, maybe
via the C_TRACE() macro, kind of how it already does in
_PyEval_EvalFrameD
Frank Ch. Eigler f...@elastic.org added the comment:
Hi -
On Wed, May 16, 2012 at 06:29:09PM +, Antoine Pitrou wrote:
[...]
No obvious error message. Who the hell designs such UIs? This seems
as stupidly unfriendly as dtrace...
Sorry about that. You're running a near-two-year-old
Frank Ch. Eigler f...@elastic.org added the comment:
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
Frank Ch. Eigler f...@elastic.org added the comment:
I believe the problem jcea is experiencing is with the
solaris (/linux?) branch of the configure.in:
if dtrace -G -o /dev/null -s $srcdir/Include/pydtrace.d 2/dev/null
It seems solaris doesn't like the -o /dev/null part. Try
specifying
