| Title: | Atari ST, TT, & Falcon |
| Notice: | Please read note 1.0 and its replies before posting! |
| Moderator: | FUNYET::ANDERSON |
| Created: | Mon Apr 04 1988 |
| Last Modified: | Tue May 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1433 |
| Total number of notes: | 10312 |
Anyone have any detailed info about how process termination gets handled by TOS/GEM ? I'm writing a monitor/debugger and seem to be running into problems in this area Consider the following : 1. Debugger loads program via PEXEC 2. User sets breakpoint in program 3. Program executed via another PEXEC 4. Program hits breakpoint and debugger takes control ( but OS still thinks program is current) 5. User has had enough and quits debugger At this point what I do is call TERMinate from within the debugger. What I expect to happen is that the program being debugged gets terminated by the OS (since it appears to be current) and control returns to the debugger at the point after the second PEXEC. e.g. as if program had called TERMinate itself. I then fix up my stack and call TERMinate a second time to exit the debugger. Although this seems to be generally correct I still get problems exiting the debugger (most often manifested by the machine hanging). Am I missing something about termination handling ? Dave.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 283.1 | LDP::WEAVER | Laboratory Data Products/Science | Tue Nov 01 1988 18:25 | 6 | |
Just guessing, but if you were to adjust the PC saved on the stack
by the breakpoint trap to point to code that does a clean exit it
may solve the problem. I leave definition of a "clean exit" to
you.
-Dave
| |||||
| 283.2 | Another shot in the dark | PRNSYS::LOMICKAJ | Jeff Lomicka | Wed Nov 02 1988 10:49 | 3 |
Perhaps you can't exit from supervisor mode? Do you get back into user mode after getting the breakpoint trap? | |||||