Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!b.gp.cs.cmu.edu!Ralf.Brown@B.GP.CS.CMU.EDU
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.os.msdos.programmer
Subject: Re: Turbo C Interrupt Question
Message-ID: <271460c8@ralf>
Date: 11 Oct 90 12:08:40 GMT
Sender: ralf@b.gp.cs.cmu.edu
Organization: Carnegie Mellon University School of Computer Science
Lines: 12
In-Reply-To: <34729@cup.portal.com>

In article <34729@cup.portal.com>, ekalenda@cup.portal.com (Edward John Kalenda) wrote:
}I may be wrong, but the way I do it is to look at the return address on the
}stack. By examining the instruction it points to (actually the instruction
}before) to see if it is an INT will tell me if it is hardware or software.

That isn't foolproof, of course.  The instruction prior to the interrupt
could end in "CD xx"....
--
UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=- 412-268-3053 (school) -=- FAX: ask
ARPA: ralf@cs.cmu.edu  BIT: ralf%cs.cmu.edu@CMUCCVMA  FIDO: 1:129/3.1
Disclaimer?    |   I was gratified to be able to answer promptly, and I did.
What's that?   |   I said I didn't know.  --Mark Twain