report at bugs
Oct 29, 2009, 10:16 AM
Post #1 of 1
(56 views)
Permalink
|
|
[issue7238] frame.f_lineno doesn't get updated after local trace function assigned to it
|
|
New submission from Mark Florisson <markflorisson88[at]gmail.com>:
As you can see, when a local trace function sets f_lineno, f_lineno
doesn't get updated on subsequent lines. Otherwise it works fine.
$ python tracer_testcase.py
12
12
12
13
14
15
The reference manual (for python 2.6) states the following: "f_lineno is
the current line number of the frame — writing to this from within a
trace function jumps to the given line (only for the bottom-most frame).
A debugger can implement a Jump command (aka Set Next Statement) by
writing to f_lineno.". This is contradictory with the shown results,
because apparently it doesn't always represent the current line number.
----------
components: Interpreter Core
files: tracer_testcase.py
messages: 94681
nosy: eggy
severity: normal
status: open
title: frame.f_lineno doesn't get updated after local trace function assigned to it
type: behavior
versions: Python 2.4, Python 2.5, Python 2.6, Python 2.7, Python 3.0, Python 3.1, Python 3.2
Added file: http://bugs.python.org/file15229/tracer_testcase.py
_______________________________________
Python tracker <report[at]bugs.python.org>
<http://bugs.python.org/issue7238>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
|
