Deleting a branch is permanent. It CANNOT be undone. Continue?
#3 PH7 Engine does not track line numbers at run-time
Closed
opened 3 years ago by belliash
·
3 comments
Labels
Milestone
No Milestone
Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
This issue currently doesn't have any dependencies.
Loading…
There is no content yet.
Delete Branch '%!s(MISSING)'
Aer Information
e53cfb8ba0Your problem description
debug_backtrace() and probably any other related function returns always 1 as a file line. Root cause is PH7 Engine not tracking line numbers at run-time. This is hard-coded in vm.c, lines: 9300 - 9304.
To implement this feature, in the compilation bytecode header must store a mapping of the opcode's position with the associated source code line.
source -> compile -> bytecodes + header with lines for each bytecode jump
This issue is a structural problem in generating the bytecode, which is necessary to generate with the header that contains this mapping.
For example, it follows the attachment how Java handles this mapping. This image is a example of method with yours bytecodes and yours lines associated.
This is connected with #2, I think. There is a general problem with information about file & line position in PH7. FILE shows some trash, while debug_backtrace() simply gets currently processed file and returns only last callback instead of whole backtrace.
gitea seems annoyingly to close the ticket once you mention it in a commit message.