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 xdegaye
Recipients belopolsky, jcea, xdegaye
Date 2013-02-24.11:34:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361705691.46.0.793470875154.issue17277@psf.upfronthosting.co.za>
In-reply-to
Content
The proposed patch fixes the backtrace line numbers issue, but it does not fix
PyFrame_GetLineNumber() which is the recommended way to get the frame line
number.

As mentionned in the original message, testing for f->f_trace to implement the
f_lineno getter is not correct. The f_lineno setter is also wrong in allowing to
modify f_lineno when the frame is not the one that is being traced (pdb prevents
that to happen though, in do_jump()).

I am working on another patch that should fix the issue by changing
PyFrame_GetLineNumber() and the f_lineno accessors.
History
Date User Action Args
2013-02-24 11:34:51xdegayesetrecipients: + xdegaye, jcea, belopolsky
2013-02-24 11:34:51xdegayesetmessageid: <1361705691.46.0.793470875154.issue17277@psf.upfronthosting.co.za>
2013-02-24 11:34:51xdegayelinkissue17277 messages
2013-02-24 11:34:51xdegayecreate