From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d8e2df437fbcbe0f
X-Google-Attributes: gid103376,public
From: Dave Wood <dpw@aonix.com>
Subject: Re: ObjectAda for windows - experiences?
Date: 1997/04/19
Message-ID: <335875BC.35AD@aonix.com>#1/1
X-Deja-AN: 235902097
Cache-Post-Path: optional.cts.com!unknown@199.164.191.83
References: <01bc4c13$415c7840$d722ea9e@P01225.logica.co.uk>
Organization: Aonix
Reply-To: dpw@aonix.com
Newsgroups: comp.lang.ada
Date: 1997-04-19T00:00:00+00:00
List-Id: <comp.lang.ada>


Nobody wrote:
[quite a moniker you have there, by the way...]
> 
> We evaluated ObjectAda for windows version 7.0 and had a lot of problems
> with the debugger; Aonix gave us good support tell use the problem is due
> to be fixed in 7.1.
> 
> But were we alone? How many other users of 7.0 had major problems with the
> debugger? Was it to do with our PC configurations or some quirk of what we
> were doing? Information on any experiences with OAW, via email, would be
> much appreciated.

The integrated debugger with 7.0 was, frankly, less than ideal.  
Subsequent patches, available on our web site, fixed a number of
key problems.  The 7.1 release which is now in final qualification
fixed even more and adds in important functionality that was 
missing from 7.0, such as register display and modify.

We actually plan to do quite a bit more with the debugger over
the next several months on our way to 7.2.  It will be an important
focus area for us.  If there are any particular goodies you'd like
to see, feel free to send to drop me an email.

Another feature you might not realize is that there are a couple 
of other ways to debug.  We include the Windbg debugger on the CD,
and you can also debug with the Visual C++ debugger (or the Visual
J++ debugger if you are working in Java mode).

> The problem we had was to do with the debugger running v. slow then
> progressively slower when single stepping - this made it pretty much
> unuseable for us.

The debugger had a response problem when certain types of windows
were open while stepping.  This problem has been eliminated.

By the way, this kind of info is generally available in the FAQ or
by calling into customer support.

-- Dave Wood
-- Product Manager, ObjectAda for Windows
-- Aonix - "Ada: To Infinity and Beyond!"
-- http://www.aonix.com