dlyons@Apple.COM (David A. Lyons) (12/08/89)
In article <1989Nov29.083420.23223@ux1.cso.uiuc.edu> jb10320@uxa.cso.uiuc.edu (Jawaid Bazyar) writes: >It's strange answering my own question. It seems a routine called earlier >did a very naughty thing, i.e. SEI. > >But I still have one question: what does the debugger need interrupts >turned on for? I realize that if I'd been smart I would have looked at the >debugger P-reg display for interrupt information, but it seems silly for the >debugger to force interrupts on. What if, for instance, there are some >interrupt handlers installed that absolutely should NOT run? Perhaps it's >fixed in a newer version... (I'm still using all the Beta software) For one thing, GSBug gets keystrokes through the Event Manager (if it's active), so interrupts need to be enabled for the key-down events to get posted. Of course, it does make tracing interrupt handlers hard sometimes. > Oh well. No one ever said interrupts were going to be any fun. 8^) Hmmm...I must've said it at some time or other. Life would be Boring without interrupts. :-) -- --David A. Lyons, Apple Computer, Inc. | DAL Systems Apple II Developer Technical Support | P.O. Box 875 America Online: Dave Lyons | Cupertino, CA 95015-0875 GEnie: D.LYONS2 or DAVE.LYONS CompuServe: 72177,3233 Internet/BITNET: dlyons@apple.com UUCP: ...!ames!apple!dlyons My opinions are my own, not Apple's.