Mail Archives: djgpp/1993/07/28/07:57:24
I still don't know why my application fails under Novell. In order to
find out which of the system calls (creat, open, lseek,fstat etc.)
fails, I would like to build a tracing function into turbo.s (turbo_assist)
Has anyone done so before. The problem is that this function
cannot use normal i/o because that in turn would imply invocation
of turbo_assist causing endless recursion.
I think, you should be able to do the tracing easily in real mode.
Just put in some debugging code into function turbo_assist in
exphdlr.c.
You might also be able to use dos-functions to write to stdout
an redirect the output.
Dieter
- Raw text -