Issue222838

classification
Title: Wrong line number in traceback when in try: finally: block.
Type: Severity: normal
Components: Core Versions:
Milestone:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: bckfnn
Priority: low Keywords:

Created on 2000-11-18.19:25:24 by bckfnn, last changed 2000-12-12.21:28:21 by bckfnn.

Messages
msg122 (view) Author: Finn Bock (bckfnn) Date: 2000-11-18.19:25:24
Wrong line number reported in stacktrace when using try ... finally.  The line
number reported is the last statement in the try: clause:, not the line with the
call to foo(). This makes debugging a little bit more diffecult.


--------------------- FILE: test179.py --------------------- 

def foo():
   assert 0

try:
   foo()
finally:
   pass

--------------------- END --------------------- 



d:\java\jpython\test>python test179.py
Traceback (innermost last):
  File "test179.py", line 6, in ?
    foo()
  File "test179.py", line 3, in foo
    assert 0
AssertionError



d:\java\jpython\test>jpython test179.py
Traceback (innermost last):
  File "test179.py", line 8, in ?
  File "test179.py", line 3, in foo
AssertionError:

msg123 (view) Author: Finn Bock (bckfnn) Date: 2000-12-12.21:28:21
Fixed in CodeCompiler.java 2.9; Py.java 2.27;

A traceback object is also created when catching
an exception in a try: finally: statement.
History
Date User Action Args
2000-11-18 19:25:24bckfnncreate