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
Latest versions of MADS on Win32 seem to have a bug with the .fl directive when emitting zero: they emit 6 extra bytes to the output, which is not reflected in the PC, corrupting the executable.
Repro case:
org $2000
.fl 0
MADS 2.1.0 build 8:
Writing listing file...
Writing object file...
2 lines of source assembled in 2 pass
12 bytes written to the object file
MADS 2.1.5 build 3:
Writing listing file...
Writing object file...
2 lines of source assembled in 2 pass
18 bytes written to the object file
The hex dump of the executable shows 6 extra bytes that should not be there, although the DOS segment header still indicates only 6 bytes ($2000-2005):
Latest versions of MADS on Win32 seem to have a bug with the .fl directive when emitting zero: they emit 6 extra bytes to the output, which is not reflected in the PC, corrupting the executable.
Repro case:
MADS 2.1.0 build 8:
MADS 2.1.5 build 3:
The hex dump of the executable shows 6 extra bytes that should not be there, although the DOS segment header still indicates only 6 bytes ($2000-2005):
This only happens with 0 and -0. Non-zero values emit 6 bytes as expected.
The text was updated successfully, but these errors were encountered: