MASM/TASM中Lee算法可视化项目的跨文件过程调用链接问题

Alright, let's break down how to resolve this cross-file procedure call issue you're facing with your Lee algorithm visualization project. I’ve dealt with this exact kind of headache back when building DOS assembly projects, so here’s a step-by-step breakdown of what you need to check and fix:

1. Properly Declare External & Public Procedures #

This is the most common mistake with cross-file calls in TASM:

• In your main code file: Use the EXTRN pseudo-instruction to declare any procedures you’re calling from the process library. The syntax is EXTRN procedure_name:TYPE, where TYPE is either NEAR or FAR (match this to your memory model—NEAR for small/compact models, FAR for large/huge). For example:

  EXTRN DrawGrid:NEAR
  EXTRN UpdateLeePath:FAR
  

• In your process library source file: Mark the procedures you want to export with the PUBLIC pseudo-instruction, right before the procedure definition. This tells the linker that these procedures are available for other files to call:

  PUBLIC DrawGrid
  DrawGrid PROC NEAR
      ; Your procedure logic here
      RET
  DrawGrid ENDP
  

2. Fix Include Directive Conflicts #

You mentioned adding the process library’s include caused issues—here’s why and how to fix it:

• Don’t include .asm files directly: Including the process library’s source file (.asm) in your main file will cause the procedure code to be assembled twice, leading to duplicate symbol errors during linking. Instead, create a header file (.inc) for your process library that only contains EXTRN declarations and constant definitions, then include that in your main file.
• Sync memory models across all files: Every assembly file (main, macro library, process library) must use the same memory model (e.g., .MODEL SMALL). Mismatched models will break procedure call addressing and cause runtime crashes.

3. Correct Assembly & Linking Workflow #

TASM assembles files individually, so you need to link all object files together properly:

1. Assemble each source file separately:

   tasm main.asm  ; Produces main.obj
   tasm proc_lib.asm  ; Produces proc_lib.obj
   

2. Link all object files and libraries:
   Use TLink to combine the object files, along with your macro library if it’s a precompiled .lib file:

   tlink main.obj proc_lib.obj,, macro_lib.lib
   

   The empty commas here are placeholders for the map file and resource file—you can fill them in if needed, but they’re optional for basic projects.

4. Troubleshoot Post-Assembly Issues #

Since TASM assembles fine but you’re having issues afterward, focus on these two areas:

• Linker errors (e.g., "Undefined symbol"): Double-check that EXTRN and PUBLIC names match exactly (TASM is case-insensitive, but consistency avoids mistakes), and that you’re linking all required .obj files.
• Runtime crashes: This is often due to stack imbalance. Ensure your procedure’s RET matches its type: use RET for NEAR procedures and RETF for FAR procedures. Also, make sure you’re not passing incorrect parameters that mess up the stack.

Example Working Setup #

To make this concrete, here’s a simplified example:

Process Library (proc_lib.asm) #

.MODEL SMALL
.CODE
PUBLIC DrawGrid
DrawGrid PROC NEAR
    ; Example: Draw a grid for Lee algorithm
    MOV AH, 09H
    LEA DX, GridString
    INT 21H
    RET
DrawGrid ENDP
GridString DB 'Lee Algorithm Grid: $'
END

Process Library Header (proc_lib.inc) #

EXTRN DrawGrid:NEAR

Main File (main.asm) #

.MODEL SMALL
INCLUDE macro_lib.inc
INCLUDE proc_lib.inc
.CODE
START:
    MOV AX, @DATA
    MOV DS, AX

    CALL DrawGrid  ; Call the external procedure

    ; Exit program
    MOV AH, 4CH
    INT 21H
END START

Assembly & Link Commands #

tasm proc_lib.asm
tasm main.asm
tlink main.obj proc_lib.obj,, macro_lib.lib

内容的提问来源于stack exchange，提问作者Chiorean Tudor