[Jython-bugs] [Bug #122838] Wrong line number in traceback when in try: finally: block.

[<no...@so...>]

Bug #122838, was updated on 2000-Nov-18 11:25
Here is a current snapshot of the bug.

Project: Jython
Category: Core
Status: Closed
Resolution: Fixed
Bug Group: None
Priority: 1
Submitted by: bckfnn
Assigned to : nobody
Summary: Wrong line number in traceback when in try: finally: block.

Details: 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:



Follow-Ups:

Date: 2000-Dec-12 13:28
By: bckfnn

Comment:
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.

-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=122838&group_id=12867