From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5265ce03ee8f5252 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-01-08 05:00:06 PST Path: supernews.google.com!sn-xit-03!supernews.com!logbridge.uoregon.edu!news.maxwell.syr.edu!sjc-peer.news.verio.net!news.verio.net!iad-read.news.verio.net.POSTED!kilgallen From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Ok sorry, it is just a book gives no feedback. Message-ID: References: <931r2l$4ai5t$2@ID-25716.news.dfncis.de> <931t08$5u5$1@nnrp1.deja.com> <932632$e0e$1@nnrp1.deja.com> <932an8$ijs$1@nnrp1.deja.com> <93421h$2ju$1@nnrp1.deja.com> <934j5c$eu9$1@nnrp1.deja.com> <937jk6$s6l$1@nnrp1.deja.com> <9386t0$av0$1@nnrp1.deja.com> <938qom$ptd$1@nnrp1.deja.com> <3A59B1E1.A4Organization: LJK Software Date: 8 Jan 2001 07:57:23 -0500 NNTP-Posting-Host: 216.44.122.34 X-Complaints-To: abuse@verio.net X-Trace: iad-read.news.verio.net 978958646 216.44.122.34 (Mon, 08 Jan 2001 12:57:26 GMT) NNTP-Posting-Date: Mon, 08 Jan 2001 12:57:26 GMT Organization: Verio Xref: supernews.google.com comp.lang.ada:3772 Date: 2001-01-08T07:57:23-05:00 List-Id: In article <3A59B1E1.A46DBE47@acm.org>, Marin David Condic writes: > Larry Kilgallen wrote: > >> Been there, done that, got the T-shirt. I detested it. >> I think one of the great debugger advances has been to >> use a small engine in the process being debugged and >> put the great bulk of the debugger (GUI, etc.) into >> another process where it will not impact addresses, >> etc. (Of course that does not eliminate the heisenbug > > I am presuming that you are talking about having a relatively small chunk of code in an > embedded app that will grab the contents of memory and send it down the wire upon request, > etc.? The concept of an on-board monitor that will load & read memory, maintain lists of > addresses to watch & report on periodically, etc. has been around for a while. They work very > nicely - especially since they remain in the production code/box so that you can actually use > them in the field if necessary. You don't need any special equipment besides the presence of > a communication link. Actually, my own concerns are more within a single general-purpose operating system where one wants a full GUI debugger interface run by one process and debugging another process. My other application, closer to yours, is for debugging kernel code on a general-purpose operating system with a separate system handling the GUI for the debugger. While the same approaches work for me as for you embedded folks, I post this reply to emphasize the diversity of interests in the newsgroup. ============================================================================== Great Inventors of our time: Al Gore -> Internet; Sun Microsystems -> Clusters ==============================================================================