Path: utzoo!attcan!uunet!olivea!decwrl!elroy.jpl.nasa.gov!sdd.hp.com!uakari.primate.wisc.edu!unmvax!pprg.unm.edu!topgun!mustang!nntp-server.caltech.edu!rknop From: rknop@nntp-server.caltech.edu (Robert Andrew Knop) Newsgroups: comp.sys.cbm Subject: Re: Debugger 2.0 Message-ID: <1991Jan23.174325.2131@nntp-server.caltech.edu> Date: 23 Jan 91 17:43:25 GMT References: Organization: California Institute of Technology, Pasadena Lines: 38 lcs@remus.rutgers.edu (Lyle C. Seplowitz) writes: > It works great (although I would have liked it to default to a >BACKRAM SuperDebugger rather than using the REU so that the rboot >ability isn't destroyed--I keep forgetting to hold the space bar). If I become ambitious, I may try to write a patch to do this. If somebody else beats me to it, well, that won't kill me either.... >The documentation file is VERY long, but informative. Its more a technical >guide, although it does briefly discuss the new comands. By the way, >it is called "The Hitchhiker's Guide to GeoProgrammer" -- is this the >one that people were asking about, or is there a "Hitchhiker's Guide >to GEOS"? This is distinct from the "Hitchhiker's Guide to GEOS," and it's name is probably a reference to that. The HHG2G contains a few informative chapters about GEOS programming (including some 128 info), then has alphabetical descriptions of all Kernal routies. There are a few described that don't appear in the PRG (e.g. FetchRAM and StashRAM), and I find the descriptions much more reliable than those in the PRG (there are also fewer typos, even though the HHG2G in the form where work on it stopped is still a rough draft!). > Anyway, my question is this: I wanted to test the debugger with a >small, incomplete program that I wrote, however, when I opened the >file, the debugger did not load in the .sym file that was produced by >the linker. I haven't relinked it lately, but that shouldn't be a >problem, the linker is the same. How can I get the debugger to load >that symbol file? Is it a .sym file or a .dbg file? What does the icon look like: two crashing musical symbols, or a hand reaching for the debugger spray can? If its the former, the debugger isn't supposed to load it- that is a geoWrite file produced for the benefit of the progammer. If it's the latter, rename it to .dbg, and the debugger may be able to find it. -Rob rknop@tybalt.caltech.edu