An Introduction Of Boundscheckers

1268 Words3 Pages

BoundsChecker
Introduction:
BoundsChecker is a utility for checking applications for bugs like memory overwrites, reading not initialized memory, use of dangling pointers and much more.It is a memory checking and API call validation tool used for C++ software development with Microsoft Visual C++. BoundsChecker is an indispensable tool for Windows programming. It finds errors very efficiently (including tons in Microsoft's code!!). Its main focus is on finding memory leaks.
Creation and Version History:
It was created by Nu-Mega Technologies in the early 1990s. When Nu-Mega was purchased by Compuware in 1997, BoundsChecker became part of a larger tool suite,DevPartner Studio. Micro Focus purchased the product line from Compuware in 2009.
Date Version Details
March 1991 2.0 For DOS
1996 4.0 Introduced API Validation feature
March 1997 5.0
1998 6.0 First version after acquisition of NuMega by Compuware.
May 2007 8.2 Last version with full support for Visual Studio 6.0 and Visual Studio .NET 2003.
Sept 2008 9.0 Supports Visual Studios 2005 & 2008.
Oct 2009 9.1 Supports Windows 7
April 2010 10.0 Supports Visual Studio 2010
Feb 2011 10.5 Supports X64 applications on Windows Vista X64 and later
April 2012 10.6 New licensing model, product update checker, preliminary support for Visual Studio 2012, and system tray tool with activity monitor.
Sept 2012 11.0 Full Visual Studio 2012 support, improved performance and accuracy.
April 2013 11.1 Chinese localization (excluding on-line help). Various bug fixes.
Jan 2014 11.2 Support for Windows 8.1, Windows 8.0 and Visual Studio 2013.

BoundsCheckers Philosophy:
To increase software quality, developers must thoroughly test their code early in the development process. Bugs must be caught and r...

... middle of paper ...

...standard API and OLE functions BoundsChecker validates to include APIs you create yourself. When it is extended to test your APIs, BoundsChecker automatically validates the parameters, validates the return values and logs the trace data for analysis.
• Windows Compliance Assurance:
In order to assure program’s ability to run on all Win32 variants, BoundsChecker checks program’s compliance against Windows NT, Windows 95, Windows 98, Windows CE 2.0 and Win32S. It also displays the program’s use of the C and C++ Run-Time Library and ANSI C Extensions.
Example:

Using the Call Stack:The stack frame lets you display the source code for any function in the stack. This is usefulfor seeing the events that led to the error. If the error involves a memory block that is allocated elsewhere, the stack frame also lets you view the point at which the memory is allocated.

Open Document