User Tools

Site Tools


blog:pushbx:2026:0204_chasing_a_warplink_bug

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
blog:pushbx:2026:0204_chasing_a_warplink_bug [2026-02-04 18:32:57 +0100 Feb Wed]
ecm created
blog:pushbx:2026:0204_chasing_a_warplink_bug [2026-02-04 18:40:00 +0100 Feb Wed] (current)
ecm mention that adding a reloc worked around the bug
Line 61: Line 61:
 The number_reloc variable also [[https://hg.pushbx.org/ecm/warplink/file/3d62e4618a5b/mlglobal.mac#l230|is initialised properly]]. The number_reloc variable also [[https://hg.pushbx.org/ecm/warplink/file/3d62e4618a5b/mlglobal.mac#l230|is initialised properly]].
  
 +Adding a segment relocation, such as generated by a ''jmp far label'' instruction, made the error go away.
  
 ===== Nondeterminism ===== ===== Nondeterminism =====
Line 166: Line 167:
 ===== Fix ===== ===== Fix =====
  
-The fix is to simply put data_fixup_count into the part of the data section that's explicitly zero-initialised by the startup code.+The fix is to simply [[https://hg.pushbx.org/ecm/warplink/rev/7d4588211863|put data_fixup_count into the part of the data section that's explicitly zero-initialised]] by the startup code.
  
  
blog/pushbx/2026/0204_chasing_a_warplink_bug.1770226377.txt.gz ยท Last modified: 2026-02-04 18:32:57 +0100 Feb Wed by ecm