Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!cunixf.cc.columbia.edu!brian
From: brian@cunixf.cc.columbia.edu (Brian Hoffman)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Summary of PC Debuggers
Summary: Yo Yo Yo
Keywords: Yo
Message-ID: <1990Apr13.203204.1735@cunixf.cc.columbia.edu>
Date: 13 Apr 90 20:32:04 GMT
References: <639911608.5585@minster.york.ac.uk>
Reply-To: brian@cunixf.cc.columbia.edu (Brian Hoffman)
Organization: Columbia University
Lines: 26

In article <639911608.5585@minster.york.ac.uk> mike@minster.york.ac.uk writes:
>> Although responses are enormous, all agreed that:
>>   Unix dbx is a toy compared to PC debuggers;
>> 2. Turbo Debugger by Borland and CodeView by Microsoft
>>   are the best.
>> Some argued that Turbo Debugger is even better. One netter said 
>> Periscope is also a very good choice.
>			   
>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:
>
>stop in my_func when my_func`var1->v_field->n_val >= main`var2.field1
>
>and
>
>when in my_func { print *my_func`var1->v_field ; set my_func`var1->v_val = 27 ; }
>
>Or is the objection that dbx only uses two colours :-)
>?????
>mike richardson

It's easy to set a watchpoint in Quick C.  The above statement would be
no problem.  I'm not so sure about Turbo C...I never did figure out how to
do that stuff in dbx.

Brian