home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.hp48
- Path: sparky!uunet!snorkelwacker.mit.edu!ira.uka.de!fauern!fauna!immd1.informatik.uni-erlangen.de!kskalb
- From: kskalb@immd1.informatik.uni-erlangen.de (Klaus Kalb)
- Subject: Re: sys_RPL EVAL??? and DEBUGer ???
- References: <1992Nov5.093538.11956@waikato.ac.nz> <MHEISKAN.92Nov5011224@lk-hp-21.hut.fi>
- Message-ID: <BxGEJG.24z@immd4.informatik.uni-erlangen.de>
- Sender: news@immd4.informatik.uni-erlangen.de
- Organization: CSD., University of Erlangen
- Date: Mon, 9 Nov 1992 14:50:03 GMT
- Lines: 24
-
- mheiskan@snakemail.hut.fi (Mika Heiskanen) writes:
- >In article <1992Nov5.093538.11956@waikato.ac.nz> fee@waikato.ac.nz writes:
-
- >>Oh yeah, and is there a routine around for single-stepping a sys_RPL
- >>routine so I can monitor what's on the stack for debugging purposes?
- >>It's very frustrating "doin' de download shuffle" and watching the HP
- >>crash because I forgot about some item on/off the stack.
-
- >Internal DBUG is the only one. Sure I've thought about programming one but
- >all the words changing the run stream, return stack or making type checks
- >on run stream made it too hard for me. Anybody else who has tried it?
-
- No, I didn't try to program a debug routine.
-
- But I frequently insert an xHALT to debug my sysRPL programs and use
- SST to step through.
- There are some commands you can't step over (LOOP, BEGIN, IF, ', ...)
- but it will work for all stack handling words. If you have a listing
- nearby you will know what those externals are supposed to do.
- ---
- ------------------------------------------------------------------------------
- Klaus Kalb | mail : IMMD1 / Martenstr. 3 / W-8520 Erlangen / Germany
- Werch ein Illtum | email: kskalb@immd1.informatik.uni-erlangen.de
- ------------------------------------------------------------------------------
-