Date:	Wed, 28 Jul 93 11:50:31 +0200
From:	kuku AT acds DOT physik DOT rwth-aachen DOT de (Christoph Kukulies)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	tracing system calls

Here's again 'hair pulling' Chris:

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. So I guess I have to 
put the trace into memory into a large array and dump it
at a certain point in my program.

Any suggestions? Or is there a way to bypass the turbo routines
for this purpose and use some console or COM int?


--Chris

- Raw text -