Xref: utzoo comp.os.msdos.programmer:3920 comp.windows.ms.programmer:1314
Path: utzoo!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!uunet!ns-mx!ccad.uiowa.edu!cadsi
From: cadsi@ccad.uiowa.edu (CADSI)
Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer
Subject: Re: Borland C++ 2.0, report #2
Message-ID: <1991Mar13.155014.14865@ccad.uiowa.edu>
Date: 13 Mar 91 15:50:14 GMT
References: <1991Mar13.144040.16579@isis.cs.du.edu>
Distribution: na
Organization: CAD-Research, U. of Iowa, Iowa City, Iowa
Lines: 17

From article <1991Mar13.144040.16579@isis.cs.du.edu>, by ebergman@isis.cs.du.edu (Eric Bergman-Terrell):
> 
> About the Windows Debugging Kernel:  What sorts of bugs does it typically
> find?  On what sorts of machines would the bugs actually cause a problem -
> or which configurations?

one of the most common is the DeleteObject call on stock object.  Non
debugging kernel will allow this and die later in unexplainable ways.
The particular machine doesn't really matter unless you are writing code
that will be specific, say to 386 enhanced mode.


|----------------------------------------------------------------------------|
|Tom Hite					|  The views expressed by me |
|Manager, Product development			|  are mine, not necessarily |
|CADSI (Computer Aided Design Software Inc.	|  the views of CADSI.       |
|----------------------------------------------------------------------------|