Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!rpi!rpi.edu!deven From: deven@pawl.rpi.edu (Deven Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: Amigix Message-ID: Date: 27 Mar 89 20:03:17 GMT References: <0282.AA0282@glyph> Sender: usenet@rpi.edu Reply-To: shadow@pawl.rpi.edu (Deven T. Corzine) Followup-To: comp.sys.amiga.tech Organization: RPI Public Access Workstation Lab, Troy NY Lines: 47 In-reply-to: nichiren@glyph.UUCP's message of 26 Mar 89 15:48:31 GMT In article <0282.AA0282@glyph> nichiren@glyph.UUCP (Andy Heffernan) writes: >In article deven@pawl.rpi.edu (Deven Corzine) complains: >> You still haven't told me much about this; I don't understand how it >> works. Sure, I get the general idea, but I need to know exactly how >> it all works so I can implement it correctly. I truly hate programs >> that run fine but randomly crash the machine when they exit. I want >> everything to work smoothly, and for that, I need to know how the Exec >> routines operate. I'd prefer not to go digging around in the ROMs >> with a disassembler if I can avoid it. >Please do. For Randell's sake please walk through some Exec code >with a single-stepper (but watch out for critical-section code!) >It's really very lovely stuff. Actually, I probably will anyway, for the experience, but the main reason for asking Randell (or anyone else who may care to answer) is that I'm more likely to know what's safe to count on and what's not. I don't want to code based on one version of exec.library, since 1.4 may change it wildly, for all I know, so I'd rather have some assurance of what is supposed to happen, and what may change in later versions of the operating system... and what I can count on. (and to what extent.) Besides, I suspect there may be others that could benefit from a clear explanation of this murky subject [meaning only that it's hard to figure out from the docs (RKM's, etc.)] and seeing as how Randell's been so wonderfully helpful hitherto, and generally explains things fairly well and knows what he's talking about, it seems worthwhile asking. >> AddTask(task,initialPC,finalPC)... >> >> Task I understand fine. I take it that AddTask starts off the task by >> pushing finalPC on the stack (as a return address for initialPC) along >> [etc.] >Open the door, get on the floor -- Everybody single-step their code... Besides, I'd rather not reverse-engineer Exec functions and work on empirical evidence. Deven -- ------- shadow@pawl.rpi.edu ------- Deven Thomas Corzine --------------------- Cogito shadow@acm.rpi.edu 2346 15th Street Pi-Rho America ergo userfxb6@rpitsmts.bitnet Troy, NY 12180-2306 (518) 272-5847 sum... In the immortal words of Socrates: "I drank what?" ...I think.