Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!motcsd!hpda!hpcupt1!hpindwa!tribby
From: tribby@hpindwa.HP.COM (David Tribby)
Newsgroups: comp.sys.apple
Subject: Re: GSBug Questions
Message-ID: <36410003@hpindwa.HP.COM>
Date: 21 Jul 89 16:48:39 GMT
References: <36410002@hpindwa.HP.COM>
Organization: HP Information Networks Group/Cupertino CA
Lines: 35

Thanks, Syd & Dave, for the answers to my GSBUG questions! I asked...
|> 1. Is there any way to set a "real time" breakpoint for a toolset call?
And Dave Lyons pointed out...

|Yes!  The version APDA has (4.0b1) has SETTBRK, TBRKIN, and TBRKOUT (among
|other things).  

TBRKIN and TBRKOUT were exactly what I needed. SETTBRK and the commands to
show and clear toolset breakpoints were described in a cover sheet for the
4.0b1 manual, but not the related IN and OUT commands. Last month you told 
me about the "R" command, to reset the init version after poking around. Are 
there any other undocumented commands that work?


|> 2. Does the "init" version of GSBug interfere with the "run time" version?
|Yes, at least sometimes.  Hold down Option during boot to keep the init from
|loading (or delete the file, or mark it Inactive in the Finder).
As Syd points out, why even use the run time version? It's real handy to have
the init version available to look around in a running program. Is there any
situation where it's better to start from the run time version?


And now a bonus question...

I go into GSBug to examine parts of a program, including tracing it for
awhile and switching between the Super Hi-Res and GSBug screens. After I've
had enough, I go to single-step mode, switch to SHR, and jump back into my
code. When my program terminates back to APW, the screen seems to be in
low-resolution graphic mode rather than text mode. Why? (I fix the screen by
re-entering GSBug and immediately exiting.)

   
--Dave Tribby
                                   - - - - -
        ARPA: tribby%hpda@hplabs.HP.COM   UUCP: hplabs!hpda!tribby