➜
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.
Created on 2010-01-14 00:49 by exarkun, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| evalframeex.patch | exarkun, 2010-01-14 00:49 | |||
| Messages (2) | |||
|---|---|---|---|
| msg97744 - (view) | Author: Jean-Paul Calderone (exarkun) *  |
Date: 2010-01-14 00:49 | |
pystack tries to detect C frames which it can extract Python frame info from. However, it still references the old, now (supposedly) unused PyEval_EvalFrame function. This leads it to never find any frames, since PyEval_EvalFrameEx is now what's actually on the stack. It should be referring to that function. Attached makes the necessary change. |
|||
| msg97747 - (view) | Author: Skip Montanaro (skip.montanaro) *  |
Date: 2010-01-14 01:16 | |
Thanks for the heads up. Should be fixed on trunk (r77484) and py3k (r77485). |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:56 | admin | set | github: 51947 |
| 2010-01-14 01:16:38 | skip.montanaro | set | status: open -> closed nosy: + skip.montanaro messages: + msg97747 assignee: skip.montanaro resolution: fixed |
| 2010-01-14 00:49:06 | exarkun | create | |