Path: utzoo!utgpu!watserv1!watmath!maytag!watstat!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Summary of PC Debuggers
Message-ID: <1948@maytag.waterloo.edu>
Date: 13 Apr 90 23:11:03 GMT
References: <639911608.5585@minster.york.ac.uk>
Sender: daemon@maytag.waterloo.edu
Reply-To: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Organization: U. of Waterloo, Ontario
Lines: 25

In article <639911608.5585@minster.york.ac.uk> mike@minster.york.ac.uk writes:
>			   
>If UNIX dbx is a toy compared to the PC debuggers, and hence by
>implication the TurboC debugger, how do i do the equivalent of:

The claim was that dbx is not as good as the Turbo Debugger, not the little
debugger built in to the TC compiler/editor.  Both of your challenges are easy
enough in TD:

>stop in my_func when my_func`var1->v_field->n_val >= main`var2.field1

Set a breakpoint at one point (or several) of my_func, which stops on the
given condition.  

>when in my_func { print *my_func`var1->v_field ; set my_func`var1->v_val = 27 ; }

I don't understand what this one does:  does it print only on entry?  If so,
just set a breakpoint at the beginning of my_func with the action being to 
log (or print, if you really want) the value of v_field, and another with
the action being to change the value of v_val.  By the way, you probably
wouldn't want to do the print:  you can watch the value of v_field
continuously.


Duncan Murdoch