DOS ain't dead - Debugging and mapping functions (MS Linker)

Debugging and mapping functions (MS Linker) (Developers)

posted by alexfru, USA, 21.03.2025, 05:02

...
> The linker (Microsoft Overlay Linker 3.65) generates a MAP-file that is
> mostly just lines like this:
> 1286:0BA2 _flip5
> 1286:0B7E _flip_range
> 31A6:3584 _flist_sel
> 1286:0E2C _fli_abs_tseek
> 21E5:0130 _fli_comp1
> 301E:0068 _fli_comp_frame
>
> Very simple and nice file format, but quite useless without some tool that
> can tell me where each function ends up after I run the EXE and functions
> are relocated?

I think those segments in the map file are relative to the base segment, where the EXE gets loaded. So, if you load the EXE into a debugger and note the base segment, you can then add the segment from the map file and that'll be the segment of the function or variable.

Alternatively, can you compile your code using the tiny memory model, where everything is in one segment?

Post reply

Complete thread:

Debugging and mapping functions (MS Linker) - lifelike, 20.03.2025, 20:59 (Developers)
- Debugging and mapping functions (MS Linker) - alexfru, 21.03.2025, 05:02
  - Debugging and mapping functions (MS Linker) - lifelike, 21.03.2025, 20:15
    - Debugging and mapping functions (MS Linker) - tom, 22.03.2025, 21:58
      - Debugging and mapping functions (MS Linker) - lifelike, 25.03.2025, 23:16
        Debugging and mapping functions (MS Linker) - Japheth, 26.03.2025, 05:03
        Debugging and mapping functions (MS Linker) - marcov, 26.03.2025, 11:03
        Debugging and mapping functions (MS Linker) - lifelike, 27.03.2025, 20:02
        Debugging and mapping functions (MS Linker) - ecm, 26.03.2025, 09:59
- Debugging and mapping functions (MS Linker) - Rugxulo, 21.03.2025, 06:20
  - Debugging and mapping functions (MS Linker) - lifelike, 21.03.2025, 20:12