PH7 Engine does not track line numbers at run-time #3

New Issue

Closed

opened 2018-07-13 06:50:33 +02:00 by belliash · 3 comments

belliash commented

2018-07-13 06:50:33 +02:00

Owner

Aer Information

Aer Version (or commit ref): e53cfb8ba0
Operating System: Linux
System Architecture (eg. arm, x86_64, ...): x86_64

Your 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.

# Aer Information - Aer Version (or commit ref): e53cfb8ba0 - Operating System: Linux - System Architecture (eg. arm, x86_64, ...): x86_64 # Your 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.

belliash added the

bug

enhancement

labels 2018-07-13 06:50:33 +02:00

bernardobreder commented

2018-07-16 23:59:22 +02:00

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.

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.

Sem Título.jpg

0 B

belliash commented

2018-07-19 13:31:16 +02:00

Author

Owner

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.

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.