|debugging firstname.lastname@example.org (David Urting) (1999-03-23)|
|Re: debugging email@example.com (1999-03-28)|
|Re: debugging firstname.lastname@example.org (Basim Kadhim) (1999-03-28)|
|Re: debugging email@example.com (David Whitten) (1999-03-28)|
|Re: debugging firstname.lastname@example.org (Robert Rehberg) (1999-03-28)|
|Re: debugging email@example.com (Norman Ramsey) (1999-04-01)|
|Re: debugging firstname.lastname@example.org (1999-04-26)|
|From:||David Whitten <email@example.com>|
|Date:||28 Mar 1999 16:56:28 -0500|
David Urting <firstname.lastname@example.org> wrote:
: Can anyone help me to find general and detailed information about
It is very difficult to help you if we have no idea what language
or system you are planning to to debug.
For example, if you plan to debug MUMPS (DSM) the relevant commands
SET $ZWATCH="local variablename" to set a watchpoint
SET $ZBREAK="LABEL+OFFSET^ROUTINE:COMMANDNUMBER>BREAK ACTION CODE"
ZQUIT in the BREAK ACTION CODE will effectively 'ignore' the break point.
ZWRITE is usefule to look at the local variables.
ZDEBUG ON will enable breakpoints flagged by $ZBREAK, the BREAK command,
and the BREAK Interrupt character.
If you are using GDB and GNAT (Ada)
there are good web pages at
that can give you a start.
There is information about debugging with Code Warrior on a Macintosh
Note the embedded space in that URL.
Of course if you had said you were debugging gcc or a real time
controller, my answers would have been different.
A good hour with a search engine will probably yield more than enough
information for your needs.
Return to the
Search the comp.compilers archives again.