[issue24565] the f_lineno getter is broken

daniel hahler added the comment: This is likely covered by existing/linked issues already, but wanted to leave it here nonetheless: Given t-pdb.py: ``` import sys def main(): sys.stdout.write("main...\n") assert 0 if __name__ == "__main__": main() ``` Without the fix from the

[issue24565] the f_lineno getter is broken

Xavier de Gaye added the comment: Fixed a bug in the implementation of PR 12419 while running the coverage.py test suite: f_lineno must be valid upon 'call' trace events. The confusion stems from the reason why until now we have prevented line jumps from 'call' trace events, see below.

[issue24565] the f_lineno getter is broken

Change by daniel hahler : -- versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue24565] the f_lineno getter is broken

Change by Xavier de Gaye : -- pull_requests: +12373 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24565] the f_lineno getter is broken

Change by Serhiy Storchaka : -- pull_requests: +5972 stage: -> patch review ___ Python tracker ___

[issue24565] the f_lineno getter is broken

Xavier de Gaye added the comment: Added PR 6233. One of the GitHub bots failed to link this issue with PR 6233. Maybe this is related to the fact that connections to bpo are currently failing intermitently with the message: An error occurred during a connection to

[issue24565] the f_lineno getter is broken

Xavier de Gaye added the comment: A trace function may also be set in extension modules by PyEval_SetTrace() and it may not use f->f_trace. This is another reason why f->f_trace cannot be used in PyFrame_GetLineNumber() to know when f->f_lineno is valid. --

[issue24565] the f_lineno getter is broken

Xavier de Gaye added the comment: I will work on it shortly. -- ___ Python tracker ___

[issue24565] the f_lineno getter is broken

Serhiy Storchaka added the comment: Could you please convert your patches to a PR Xavier? -- nosy: +serhiy.storchaka ___ Python tracker

[issue24565] the f_lineno getter is broken

New submission from Xavier de Gaye: The last paragraph of Objects/lnotab_notes.txt explains that the f_lineno member of the PyFrameObject structure is needed to store the line number of the last line tracing event so that this value may be used as the line number of the return event instead

[issue24565] the f_lineno getter is broken

Xavier de Gaye added the comment: Uploading the corresponding test cases. -- Added file: http://bugs.python.org/file39866/f_lineno_tests.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24565

[issue24565] the f_lineno getter is broken

Changes by Xavier de Gaye xdeg...@gmail.com: -- type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24565 ___ ___ Python-bugs-list