Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!caen!kuhub.cc.ukans.edu!maverick.ksu.ksu.edu!hoss!fergvax!231b3678
From: 231b3678@fergvax.unl.edu (Phil Dietz)
Newsgroups: comp.sys.amiga.programmer
Subject: SAS 'C' CodeProbe wanted options!!!
Message-ID: <1991Apr03.222040.1601@hoss.unl.edu>
Date: 3 Apr 91 22:20:40 GMT
Sender: news@hoss.unl.edu (Network News Administer)
Organization: Comp Sci and Engr, Univ. of Nebr.
Lines: 22

CodeProbe is nice, but it's missing some features!  If you, SAS, are reading
this, please incorporate these options....
 
1)  I'd like to have an interrupt key.  It takes forever to step through a 
program.  I'd like to GO (run) a program, then when the program is running
at a certain point (like trapping menus, etc.) I could press ESC or Amiga-ESC
etc.  It will then give control back to CodeProbe for single stepping....
 
2)  I'd like to have CodeProbe pipe the dissassembly to a file for printing.
I generally use codeprobe directly of executables, so source is not to use 
omd.
 
3)  I'd like to be able to save where I'm at in my single-stepping session.
REASON:  when my program crashes inside of cpr, I have to step through the
whole mother again (and try to remember the statement that did it!)
 
Phil Dietz

---                    
   I don't like to flame!                                    Phil Dietz 
   You know what?                              231b3678@fergvax.unl.edu       
   Newton and Leibniz suck big time!                  Univ. of Nebraska