You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is probably very little we can do about this as linenrs do not seem to be embedded in the p-code that is generated, but are derived / generated by the pc-loader that is used.
Flattened source does include pre-processor markers that include original line nrs (see #14 for an example), but this is lost in the source->binary transformation (as ktrans.exe does not support any of this).
There is probably very little we can do about this as linenrs do not seem to be embedded in the p-code that is generated, but are derived / generated by the pc-loader that is used.
I just might've found a way around this, as it turns out the linenrs are actually embedded in the p-code. This will require some trickery, but it would seem to be possible.
A problem is that in the case of embedded code (ie: %INCLUDE of a .kl file) it's not clear which line nr should be shown.
Need to investigate what the behaviour of plain ktrans is in such a case.
Example:
There is no line 747 in
PROGNAME
, or at least, not in the non-preprocessed source of it.The text was updated successfully, but these errors were encountered: