DOS ain't dead

Watcom 1.9 stack corruption after return from function (Developers)

posted by bencollver , 05.07.2026, 05:09

> No, that's right, as the retf 0x0c pops the six pushes of the arguments
> (other functions don't have as many arguments, so they're wholly passed in
> registers). If you're getting stack corruption, it's not because of that.

Thanks for the hint, i think it will help.

The awka_insertop() declaration in da.c has 6 arguments:

void
awka_insertop(int op, char *cval, char *carg, int minst, char *file, int line)
{

The awka_insertop() prototype in code.c has 5 arguments:

void awka_insertop(int, char *, char *, int, int);

And dump_code() indeed calls it with 5 arguments instead of 6.

I guess it's GIGO and it's on me to fix it.

Complete thread:

• Watcom 1.9 stack corruption after return from function - bencollver, 05.07.2026, 01:12 (Developers)
  • Watcom 1.9 stack corruption after return from function - jadoxa, 05.07.2026, 04:18
    • Watcom 1.9 stack corruption after return from function - bencollver, 05.07.2026, 05:09
      • Watcom 1.9 stack corruption after return from function - Rugxulo, 05.07.2026, 07:10
      • Watcom 1.9 stack corruption after return from function - jadoxa, 05.07.2026, 08:21
        • Watcom 1.9 stack corruption after return from function - bencollver, 05.07.2026, 15:24