Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!sdd.hp.com!wuarchive!uunet!nwnexus!adonis1
From: adonis1@nwnexus.WA.COM (Adonis Corporation )
Newsgroups: comp.sys.next
Subject: Re: Experiences with BugByte
Message-ID: <506@nwnexus.WA.COM>
Date: 10 May 91 04:53:26 GMT
References: <8c_3pp600WBME2aUYU@andrew.cmu.edu> <23467@lanl.gov>
Reply-To: adonis1@nwnexus.UUCP (Adonis Corporation (Doug Kent))
Organization: Northwest Nexus Inc.; Seattle, WA
Lines: 27

In article <23467@lanl.gov> bedney@lanl.gov (Bill Edney) writes:
>In article <8c_3pp600WBME2aUYU@andrew.cmu.edu> ls1i+@andrew.cmu.edu (Leonard  
>John Schultz) writes:
>> Has anyone heard or had any experiences with BugByte, the graphic
>> symbolic debugger from ONyX Systems?
>> 
>> Len
>
>I have purchased and am using BugByte, what do you want to know?
>
How does it compare to the gnu debugger?

How about a general summary of its features?  What do they really mean
when they say 'graphic'.  Is it really graphic, and in what respect?
Is it robust?

How does one set breakpoints, examine the contents of variables, 
does it expand structures?  How do you trace through executing code?  
Can you examine/trace through at the assembler level? 

Just a few simple question like that...

Thanks,

Doug Kent
Independent NeXT Developer (what does that really mean?)
adonis1@nwnexus.wa.com