Date:	Thu, 27 Jan 2000 07:17:53 +0500 (MVT)
From:	Prashant TR <prashant_tr AT yahoo DOT com>
To:	arcadepreserv AT hotmail DOT com
cc:	djgpp AT delorie DOT com
Subject:	Re: How Do I catch a "printf interrupt" ?
In-Reply-To:	<86n3vr$dll$1@nnrp1.deja.com>
Message-ID:	<Pine.LNX.4.10.10001270715070.574-100000@yahoo.com>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 26 Jan 2000 arcadepreserv AT hotmail DOT com wrote:

> I am doing a frontend to an MSdos application, i.e. another msdos
> application is started from my frontend, and I need to decode the
> output from this application.
> 
> I think it is possible to trap a interrupt that accurs when a call to
> printf is made, and then read the string a pointer is pointing to.

Don't know if trapping the call helps. It would create a nuisance if not
done properly.

In some of my programs (where I use this same strategy), I write the
back-end so that it redirects the output to a file rather than a screen.
Thenm  you'll only need to parse the output file rather than
handling the interrupt each time it occurs. Maybe, this can help.

- Raw text -