Please recommend Debugging tools

Ed Peddycoart

unread,

Apr 29, 1998, 3:00:00 AM4/29/98

to

I am in need of a debugging tool. I am considering Bounds Checker. Any
opinions on this product, or recommendations of a different product?

Ed

--
----------------------------------------
----------------------------------------
The opinions expressed, and statements
made, in this communication are MY OWN.
----------------------------------------
Ed Peddycoart
pedd...@nichols.com
Research Scientist
Tactical Simulation Analysis Directorate
Nichols Research Corporation
Huntsville, Alabama
----------------------------------------
"For I am the Lord, your God, who takes
hold of your right hand and says to you,
Do not fear; I will help you.
(Isaiah 41:13)
----------------------------------------

Chris Marriott

unread,

Apr 29, 1998, 3:00:00 AM4/29/98

to

Ed Peddycoart wrote in message <35479596...@nichols.com>...

>I am in need of a debugging tool. I am considering Bounds Checker. Any
>opinions on this product, or recommendations of a different product?

BC is a superb product. I've used it for many years and would thoroughly
recommend it.

Chris
----------------------------------------------------------------
Chris Marriott, SkyMap Software, UK (ch...@skymap.com).
Visit our web site at: http://www.skymap.com
Astronomy software written by astronomers, for astronomers.

brad_...@yahoo.com

unread,

Apr 30, 1998, 3:00:00 AM4/30/98

to

I would suggest getting more than one debugging tool!

I've used Bounds Checker, with some success, and I've used Purify, with a
little bit more success.

I've used these tools on the same "program" and both have turned up problems
that the other has missed.

Under NT, one of my favorite tools is the task manager. It's free, and can
tell you a lot about what's going on in you program.

If you're working with MFC, another great tool is DEBUG_NEW. If you've
created some objects, not using a wizard, add the following code to the
implementation file, after the #includes

#ifdef _DEBUG
#define new DEBUG_NEW
#undef THIS_FILE
static char THIS_FILE[] = __FILE__;
#endif

When you terminate your program, check the output window for memory leaks.

The best debugging tool, however, is experience.

Good Luck!

In article <35479596...@nichols.com>,

pedd...@nichols.com wrote:
>
> I am in need of a debugging tool. I am considering Bounds Checker. Any
> opinions on this product, or recommendations of a different product?
>

> Ed
>
> --
> ----------------------------------------
> ----------------------------------------
> The opinions expressed, and statements
> made, in this communication are MY OWN.
> ----------------------------------------
> Ed Peddycoart
> pedd...@nichols.com
> Research Scientist
> Tactical Simulation Analysis Directorate
> Nichols Research Corporation
> Huntsville, Alabama
> ----------------------------------------
> "For I am the Lord, your God, who takes
> hold of your right hand and says to you,
> Do not fear; I will help you.
> (Isaiah 41:13)
> ----------------------------------------
>

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/ Now offering spam-free web-based newsreading