John Levon <movem...@users.sourceforge.net> added the comment:
Yes, my mistake. I noticed this typo in the original patch:
207 +PyObject *
208 +PyEval_EvalFrameexEx(PyFrameObject *f, int throwflag))
Can you:
- verify that HAVE_DTRACE is indeed defined for ceval.c
- do an nm on ceval.o and look which Eval* functions you do have
Somehow, PyEval_EvalFrameEx seems not to be ending up in the .o file. It
should be easy for you to work out why...
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue4111>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
