Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!dino!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!jb10320
From: jb10320@uxa.cso.uiuc.edu (Jawaid Bazyar)
Newsgroups: comp.sys.apple
Subject: Re: Heartbeat Blues
Message-ID: <1989Dec1.182211.26517@ux1.cso.uiuc.edu>
Date: 1 Dec 89 18:22:11 GMT
References: <8222.infoapple.net@pro-generic>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: jb10320@uxa.cso.uiuc.edu (Jawaid Bazyar)
Organization: University of Illinois at Urbana-Champaign
Lines: 22

In article <8222.infoapple.net@pro-generic> ericmcg@pro-generic.cts.com (Eric Mcgillicuddy) writes:
>In-Reply-To: message from jb10320@uxa.cso.uiuc.edu
>
>It seems to me the debugger replaces the instruction with a BRK instruction
>and then traps the interupt whern it hits it. If the interupt were disabled
>would this affect the BRK? I would like to know since I am working with
>interupts on my own project and am having a rough time of it.

   I don't think so.  As far as I've noticed, the debugger breakpoints only
function during a step or trace operation.  I manually use the BRK breakpoint
method when I need to run my code at full-speed.  Even if the debugger worked
that way, a SEI only affects external, hardware IRQs.  BRK being a software
interrupt is not affected. 
   I haven't seen the new debugger (1.1). Does anyone have it?  Is it better?
Will APW ever have symbolic debugging?  The answers to these questions, and
more, tomorrow on "AIIDTS Talks". :-)


--
Jawaid Bazyar               | This message was posted to thousands of machines
Junior/Computer Engineering | throughout the entire civilized world. It cost
jb10320@uxa.cso.uiuc.edu    | the net hundreds, maybe thousands of dollars.