info-mac@uw-beaver (12/13/84)
From: dual!proper!crunch@Berkeley I have a very wierd problem using the MDS1 debugger on the Macintosh. I would like to know if anyone out there in ARPA LAND might shed some light on the subject. Here are my operating conditions. I have a Fat Mac running on the RamDisk (Apple's release-- the one with the thermometer). The following files are on the disk: Macsbug - 128k version Edit Asm Link System - using 3 desk accessories and 4 fonts (About 64k) My application is split in 4 seperatly compiled modules. I put a DC.W $FF01 in the source where I want to Single-step. Then after the 4th instruction, My PC (Program counter) jumps up into the rom. I then notice that the PC is in the ROM area. Exact address not known exactly, but I do a "WH PC" to determine which ROM trap call was executed and I determine it to be the PinRect routine. After my PC jumps up there, the system is gone because when I type "ES" (Exit to shell), the system goes back to the finder but the mouse interrupts are ignored. Is there anything My program is doing to trash the system? or has anyone else come up with strange things like this. Then after re-booting the Ramdisk again, I re-edit the DC.W $FF01 instruction at a different location, and the same problem occurs after exactly 4 steps through the code. I find this extremly annoying and would really like to find the cause. Please reply to: Dual!proper!crunch@berkeley.arpa. thanx: John T. Draper AKA Cap'n Crunch