Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [3 earlier articles] |
| Re: How do debuggers work? pardo@cs.washington.edu (1991-12-04) |
| Re: How do debuggers work? plains!ortmann@uunet.uu.net (1991-12-04) |
| Re: How do debuggers work? hasan@emx.utexas.edu (1991-12-04) |
| Re: How do debuggers work? meissner@osf.org (1991-12-05) |
| Re: How do debuggers work? gaynor@remus.rutgers.edu (1991-12-05) |
| Re: How do debuggers work? bliss@sp64.csrd.uiuc.edu (1991-12-05) |
| Re: How do debuggers work? cherrman@borland.com (1991-12-06) |
| Re: How do debuggers work? jnelson@gauche.zko.dec.com (1991-12-09) |
| Re: How do debuggers work? meissner@osf.org (1991-12-15) |
| Re: How do debuggers work? tedg@apollo.HP.COM (1991-12-19) |
| Newsgroups: | comp.compilers |
| From: | cherrman@borland.com (Conrad Hermann) |
| Summary: | Low-level debug kernels |
| Keywords: | debug, design |
| Organization: | Borland International |
| References: | 91-12-003 91-12-029 |
| Date: | Fri, 6 Dec 1991 22:12:03 GMT |
In addition to debug symbols, you need a control mechanism for the debugger
to control the task being debugged. Unix and OS/2 have a system mechanism
(ptrace?) that allows you to grab onto a process, read & write its memory,
tell it to run, step or stop, etc.
Does anyone have any pointers to interesting other OS debug kernel functions?
Are there other ways of defining an OS debugging interface? I remember
a Modula system where the debugger ran as a coroutine (PROCESS)
along with the program.
-- Conrad Herrmann
[SYR4 has /proc, a file system where each "file" name is the PID of an active
process, with the contents of the file being the memory image and some ioctl()
calls for futzing with the process. Plan 9 takes this farther and makes each
process a directory with reading and writing the contained files the way to
look at the manipulate the process. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.