Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!umd5!cgs
From: cgs@umd5.umd.edu (Chris G. Sylvain)
Newsgroups: comp.sys.ibm.pc
Subject: Re: More assembly questions about TSR development.
Message-ID: <4847@umd5.umd.edu>
Date: 5 May 89 17:25:44 GMT
References: <4550@tekigm2.MEN.TEK.COM> <5060057@hpccc.HP.COM>
Reply-To: cgs@umd5.umd.edu (Chris G. Sylvain)
Organization: University of Maryland, College Park
Lines: 24

In article <5060057@hpccc.HP.COM> tomj@hpccc.HP.COM (Tom Johnson) writes:
>
>I wouldn't do this just to run with CodeView though.  CodeView ain't too
>good for TSR debugging.  As far as I could tell, once you "terminate and
>stay resident," CodeView is done and you can't debug your actual routine.
>I'm also pretty sure you can't debug the interrupts with CodeView.
>

I've used CodeView for TSR debugging. If fact, my TSR installed an interrupt
handler which I debugged with CodeView.

You're right, once your program has invoked the TSR call, all CodeView
reports in the return value from the call (you're not still using INT 27h,
are you??)... To continue debugging, you need to modify CodeView's CS:IP.

Set CS:IP to the address of your interrupt handler (of course, don't attempt
any of this if you've taken over the keyboard handler). Single-step your
way through until you reach your IRET. Voila! You've just used CodeView
to debug an interrupt handler.
-- 
--==---==---==--
.. Came whiffling through the tulgey wood, ..
   ARPA: cgs@umd5.UMD.EDU     BITNET: cgs%umd5@umd2
   UUCP: ..!uunet!umd5.umd.edu!cgs