#741: Line numbers in backtraces are substantially wrong.
------------------------------+---------------------------------------------
Reporter: Austin_Hastings | Type: bug
Status: new | Priority: normal
Milestone: | Component: none
Version: 1.2.0 | Severity: low
Keywords: pir,line numbers | Lang:
Patch: | Platform: linux
------------------------------+---------------------------------------------
This may duplicate or supersede
[http://rt.perl.org/rt3/Public/Bug/Display.html?id=40204 RT 40204] and (by
extension) [http://rt.perl.org/rt3/Public/Bug/Display.html?id=38594 RT
38594].
Earlier tickets (above) claim that there is an off-by-one error in
diagnostics. This bug is now an off-by-a-huge-amount error.
In my example files, I get an error with a backtrace. The trace looks
like:
{{{
positional inside named args at position 2
current instr.: 'close;close;TypeInfo;main' pc 129 (try.pir:87)
called from Sub 'close;close;TypeInfo;main' pc 567 (try.pir:0)
called from Sub 'close;close;TypeInfo;init' pc 606 (try.pir:303)
called from Sub 'close;close;TypeInfo;main' pc -1 ((unknown file):-1)
}}}
In fact, there is no correlation between the line numbers printed and the
Sub names given. The 'init' sub runs from try.pir:353-358, and the 'main'
sub runs from try.pir:288-347.
(To run the attached files, which take a lot of code to accomplish
nothing, put them in the same directory and run `parrot try.pir`.)
Note that there is a suggestion in RT# 40204 that line number information
is being emitted wrong into the pbc files.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/741>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
