This is an updated, private fix, of the VisualAge C++ for Windows Version 3.5
debugger.  It contains all the fixes included in fixpak4 (i.e. WTU354),
plus the exception filtering enhancement discribed below.  Please note that
this version of the debugger has not been fully tested.


New Debugger Exception Filtering Behaviour
------------------------------------------
An enhancement has been added to the debugger to allow the user to
specify whether the debugger should stop for an exception only if
it is unhandled (i.e. no exception handler installed for it) or to
always stop for the exception.

Before this addition, the debugger always stopped for an exception, even
if there was an exception handler installed for it.  This was a bit of
an inconvenience for debugging code that threw exceptions and caught them
as part of its normal processing.

The default list of exceptions the debugger stops for is the same as
before, except that it is now only for unhandled versions of the exceptions.

To change the exception filtering behaviour of the debugger, go to the
Options -> Debugger settings -> Exception filtering... dialog.
Note that every exception in now listed twice, with the second one having
"unhandled" marked beside it.

For example:

      Access Violation
      Access Violation (unhandled)

If you select the first one, the debugger will always stop when an
access violation exception occurs.
If you select the second one, the debugger will only stop when an
access violation occurs and there is no handler registered to handle it.



Enjoy.

VisualAge Debugger Team