[Nasm-bugs] [Bug 3392794] New: Error listing, wrong error line numbers

[noreply-nasm at dev.nasm.us]

https://bugzilla.nasm.us/show_bug.cgi?id=3392794

            Bug ID: 3392794
           Summary: Error listing, wrong error line numbers
           Product: NASM
           Version: 2.15.xx
          Hardware: PC
                OS: Windows
            Status: OPEN
          Severity: normal
          Priority: Medium
         Component: Assembler
          Assignee: nobody at nasm.us
          Reporter: erdogantan at singlix.com
                CC: chang.seok.bae at intel.com, gorcunov at gmail.com,
                    hpa at zytor.com, nasm-bugs at nasm.us
     Obtained from: Binary from nasm.us

Created attachment 411844
  --> https://bugzilla.nasm.us/attachment.cgi?id=411844&action=edit
Screenshot shows correct and wrong error line numbers

For a long time I am using NASM for compiling/asembling my retro unix 386
kernel (a derivation of PDP-11 unix v1)

When asm source code of main source file (unix386.s) or included files (u1.s,
u2.s etc.) has an syntax eror or label error,

NASM gives wrong error line numbers when i use NASM v2.15 to assemble source
code.

But if I use NASM v2.11 it gives correct error line numbers of source code
files.

(I have tested 32 bit and 64 bit NASM v2.15 both are giving wrong line
numbers..)

Assembling is successful as building retro unix kernel (v1.0, 1.1 and v1.2) and
running operating system..
Kernel source code is flat (not segmented) 32 bit (80836 registers, protected
mode) code starts from offset 0 (org 0) and it has a bss (unitialized data)
section at the end. 

Defined structure and data (files) are included after included code (files).
((Also gives label address/location errors in bss section if i put -include-

sctructure definions in bss section before bss labels of relevant structure.
But error line numbers bug is a separate and important bug because
there is a bad written error-line reporting code in NASM v2.15.)

-- 
You are receiving this mail because:
You are watching all bug changes.
You are on the CC list for the bug.