Does anyone know why I get an access violation every time I run a
program to completion under Borland's Turbo Debugger GX?  It doesn't
matter whether it is assembly that is exited with

PUSH    0
PUSH    0
CALL    DosExit

or Borland's C++ for OS/2 v1.5 exited with

return 0?

There is no problem if run from the command line, but the debugger gives
an access violation EVERY TIME!  It occurs in DOSCALLS1.DLL, I think.
Wait a minute and I will check this. . . . .nope, it is DOSCALL1.DLL.
The line that is highlighted is
0x1BF96B47 LSS ESP,[ESP]
As a matter of fact, my two test programs are the TASM program

        .486
        .model  os2 flat, syscall
        includelib os2.lib
        .stack
        .data
        .code
        .startup
        .exit 0
        end

and

void main(void)
{
}

---
 * MR/2 2.0 #99 * Internet: bob.liles{at}tpl-bbs.com   RIME: ->7

--- QScan v1.14b / 01-0169