DOS ain't dead

Debugging HX applications under WD for DOS (Developers)

posted by Rugxulo , Usono, 29.08.2017, 01:09

> I want to make protected mode DOS programs using HX DOS Extender in
> assembler.
> Before I write anything complicated, I'm trying to get the debugging
> environment to work (WD.EXE) and I am having problems.

Okay (although I haven't debugged a lot under WD myself).

> After much experimenting with JWASM, I gave up on it and went with plain
> WASM.

Why exactly? JWasm is much better.

> All of the examples in HX say to use MASM + LINK but I do not have the
> latest versions of the Microsoft tools.

You shouldn't need them. JWasm + JWlink were Japheth's preferred tools.

> Can anyone help me get the local and global variables to show up under WD
> using the below program as an example? Further down I give the exact
> command-line for WASM and WLINK that I used.
>
> Here were my exact options:
> ======================
> WASM -D1 -Fo=sample.obj sample.asm
> WLINK @sample.lnk

Doesn't WASM go up to -d3 ? Maybe you didn't set it high enough?

AFAIK, default debugging info is Dwarf, but there are other variants available (e.g. older "watcom" or CodeView). Some may work better (or worse) than others. Not sure if they fully work for DOS, though.

BTW, Japheth also modified (fixed) WD.EXE, so you may wish to try that variation as well: japheth-wd.zip

Otherwise, dunno, try asking on news://openwatcom.contributors , they seem minimally active.

Complete thread:

• Debugging HX applications under WD for DOS - danielnice, 28.08.2017, 21:21
  • Debugging HX applications under WD for DOS - Rugxulo, 29.08.2017, 01:09
    • Debugging HX applications under WD for DOS - danielnice, 29.08.2017, 15:43