pushbx wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Mid early September work on the debugger ======

**2026-09-13**

This week I mostly worked on enabling different build options for the debugger, including _SYMBOLIC. One fix to the immediate assembler (immasm) also got done.

The symbolic option changes to the debugger depend on an earlier change:

<blockquote>[[https://hg.pushbx.org/ecm/ldebug.exp/rev/ccfdb5dbf541|Add symsnip directory include option]] to the makefile. This is a step towards supporting the _LINK _SYMBOLIC build, albeit not sufficient. It may eventually come down to including symsnip (and scanptab) as subrepos of the lDebug repo so that the makefile knows exactly where to find these source files, so that the dependency checks can be done in the expected way.

<cite>[[blog:pushbx:2026:0823_mid_late_august_work_multi-aliases#ldebug|lDebug section of 2026-08-23 post]]</cite></blockquote>

For now, the symsnip files live in a separate repo, just like scanptab and lmacros. They're not properly tracked as dependencies by the makefile. Moving some or all of these into hg subrepos would fix the path relative to the ldebug/source/ directory so that the proper makefile dependencies could be added. Or, the relative path could be hardcoded without using subrepos, assuming that the other repos are in sister directories of the ldebug repo.


===== lDebug (experimental repo) =====

  * doc: [[https://hg.pushbx.org/ecm/ldebug.exp/rev/5a6d537fb288|Delete some superfluous blank lines in eldcomlevels section]], left over from editing.
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/4d3eb4bbb105|Fix JMP FAR imm and CALL FAR imm in the immediate assembler]] to use the current debuggee CS as destination segment or selector, rather than the immasm code seg/sel. This change had me review much of the immediate assembler code.

The immediate assembler is rather baroque, particularly its handling of the special cases involving ip, cs, or ds. One question I had is how is a near JMP imm handled. Tracing an immasm command I found that [[https://hg.pushbx.org/ecm/ldebug.exp/file/0d63b2d851e0/source/immasm.asm#l282|the rel8 flag (dif6_immasm_rel8) is set]] for such an instruction. How so? It turned out that a near JMP imm first runs [[https://hg.pushbx.org/ecm/ldebug.exp/file/0d63b2d851e0/source/aa.asm#l2403|the assembler's code for a short JMP imm]]. This sets [[https://hg.pushbx.org/ecm/ldebug.exp/file/0d63b2d851e0/source/aa.asm#l2453|the immasm_rel8_target variable, and the flag]], and then actually assembles using a rel8 of 0 so the short JMP form (EBh) is always selected. That's how a ''. jmp 0000'' or ''. jmp 8000'' is always handled by the rel8 code in the immediate assembler, and behaves as expected.

There is an unintended even more ingenious way that occurs in a different case: if ''. jmp near 8000'' is entered, then the assembler's rel8 code runs first as before, but [[https://hg.pushbx.org/ecm/ldebug.exp/file/0d63b2d851e0/source/aa.asm#l1831|the alloweddist check will reject]] the modified rel8 encoding despite the all-zeroes rel value. The assembler goes on to encode the jump as an actual rel16 jump (E9h). But the flag and target variables are still set by the rejected rel8 handling, so everything works out as desired even though the assembler emitted the E9h jump.

The remaining changes concern building with different options, chiefly initiated by allowing the _SYMBOLIC option to build again.

  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/3ae2020c19a5|Use the SOURCEFILENAME define]] for disambiguating wlcalc and wllist symbols instead of _%%%%_FILE_%%%%_, as the latter may contain slashes.
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/2a650ca76142|Add symbols to extern.mac needed for assembling _SYMBOLIC build]] (without _PM).
  * In run.asm [[https://hg.pushbx.org/ecm/ldebug.exp/rev/caa0f6cbfae2|add _LINK conditionals]] using wlcalc for adding two extern symbols.
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/055d34cd7042|Move symbolasm_error equate for error into debug.asm]], as [[https://github.com/netwide-assembler/nasm/issues/207|NASM doesn't allow to have an equate refer to an extern symbol]] (slightly different variant of this error but also involves an equate, now I added [[https://github.com/netwide-assembler/nasm/issues/207#issuecomment-5654465901|a new test case]] in which an extern equate is defined as an equ of an extern label).
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/7fdea10c3302|Default to enable _DUALCODE]] for _SYMBOLIC _PM=0 build.
  * In xxshared.asm [[https://hg.pushbx.org/ecm/ldebug.exp/rev/5f5005cca270|avoid a line_out size calculation for _LINK_COMPAT]] as _LINK build cannot calculate it. (wlcalc could be used, but wouldn't be hardened to allow either a byte or a word operand for the result.)
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/207b660f1cd3|Add extern directives]] for _SYMBOLIC _PM build, _DX, and _EMS builds.
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/672fe828911a|Default to enable _SYMBOLASMDUALCODE option define]]. _PM _DEBUG _DEBUG_COND _SYMBOLIC build overflows first code section without it.
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/21e88b2ff5f3|Fix x.eld build to define the _LINK_COMPAT define]] needed since [[https://hg.pushbx.org/ecm/ldebug.exp/rev/5f5005cca270|the xxshared.asm change]].
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/8dc2b9747677|Rename _SYMBOLASMDUALCODE to _SYMBOLSASMDUALCODE]] to reflect the filename symbols.asm more.
  * [[https://hg.pushbx.org/ecm/ldebug.exp/rev/0d63b2d851e0|Add extern directives]] for several more options.


===== symsnip =====

  * In insert.asm stand-alone code, [[https://hg.pushbx.org/ecm/symsnip/rev/e5a705001571|use addsection directive]] to avoid convlist.pl error for symbolic -f obj lDebug build.
  * [[https://hg.pushbx.org/ecm/symsnip/rev/7805a1fbaec1|Use wlcalc for _LINK build of debugger]] with the _SECOND_SLICE or _BUFFER_86MM_SLICE options. The wlcalc uses are for shifting size symbols to obtain word sizes.

{{tag>ldebug symbolic symsnip}}


~~DISCUSSION~~