➜

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 movement
Recipients belopolsky, bretthoerner, chrismiles, danchr, jcea, laca, movement, rhettinger, robert.kern, ronaldoussoren, sirg3, skip.montanaro, twleung
Date 2009-04-22.21:17:35
SpamBayes Score 4.387066e-05
Marked as misclassified No
Message-id <1240435056.83.0.655098164584.issue4111@psf.upfronthosting.co.za>
In-reply-to
Content 
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...
History
Date User Action Args
2009-04-22 21:17:36movementsetrecipients: + movement, skip.montanaro, rhettinger, jcea, ronaldoussoren, belopolsky, bretthoerner, laca, twleung, robert.kern, sirg3, chrismiles, danchr
2009-04-22 21:17:36movementsetmessageid: <1240435056.83.0.655098164584.issue4111@psf.upfronthosting.co.za>
2009-04-22 21:17:35movementlinkissue4111 messages
2009-04-22 21:17:35movementcreate