Recommend debugger (i.e. BoundsChecker, etc...)?
-
Hi All, I am considering getting a Windows debug tool such as BoundsChecker (the only such program that I am even a little familiar with). I am looking for opinions on the usefulness of these tools, and specific recommendations for products. Who are BoundsChecker's competitors? I seem to recall a tool called Purify, but can' really think of much else. It seems like the market for these tools is diminishing (there aren't even any adds for debuggers in recent issues of MSDN magazine). Is this because the debugger in Visual Studio is good enough? Any opinions and advice will be greatly appreciated. Thanks very much, Sean
-
Hi All, I am considering getting a Windows debug tool such as BoundsChecker (the only such program that I am even a little familiar with). I am looking for opinions on the usefulness of these tools, and specific recommendations for products. Who are BoundsChecker's competitors? I seem to recall a tool called Purify, but can' really think of much else. It seems like the market for these tools is diminishing (there aren't even any adds for debuggers in recent issues of MSDN magazine). Is this because the debugger in Visual Studio is good enough? Any opinions and advice will be greatly appreciated. Thanks very much, Sean
I rely on BC to help out when things get tricky. VC's debugger (at least in VC6) can't catch the things BC can: dangling pointers, resource and global memory leaks, array out of bounds, uninitialized, etc..
Smaller Animals Software, Inc. http://www.smalleranimals.com
-
Hi All, I am considering getting a Windows debug tool such as BoundsChecker (the only such program that I am even a little familiar with). I am looking for opinions on the usefulness of these tools, and specific recommendations for products. Who are BoundsChecker's competitors? I seem to recall a tool called Purify, but can' really think of much else. It seems like the market for these tools is diminishing (there aren't even any adds for debuggers in recent issues of MSDN magazine). Is this because the debugger in Visual Studio is good enough? Any opinions and advice will be greatly appreciated. Thanks very much, Sean
I use BoundsChecker. For me is all that I need for debug my programs, detect memory leaks, optimization of codes, etc. I personally think that never will change the bounschecker of other tool. It's only my opinion. Carlos Antollini. :bob: When is Friday? In three days Bob....
-
Hi All, I am considering getting a Windows debug tool such as BoundsChecker (the only such program that I am even a little familiar with). I am looking for opinions on the usefulness of these tools, and specific recommendations for products. Who are BoundsChecker's competitors? I seem to recall a tool called Purify, but can' really think of much else. It seems like the market for these tools is diminishing (there aren't even any adds for debuggers in recent issues of MSDN magazine). Is this because the debugger in Visual Studio is good enough? Any opinions and advice will be greatly appreciated. Thanks very much, Sean
The debugger in VC6 is pretty decent (I wish it would expand macros and reveal the value of constants). Boundschecker sometimes falsely identifies memory leaks, but is good at pointing out where leaks might be occurring in other code (Stingray libraries for instance). It's a good add-on, but I only use it as a last resort, and as a last resort tool, I don't see it was being worth the relatively excessively high price. To hell with those thin-skinned pillow-biters. - Me, 10/03/2001
-
Hi All, I am considering getting a Windows debug tool such as BoundsChecker (the only such program that I am even a little familiar with). I am looking for opinions on the usefulness of these tools, and specific recommendations for products. Who are BoundsChecker's competitors? I seem to recall a tool called Purify, but can' really think of much else. It seems like the market for these tools is diminishing (there aren't even any adds for debuggers in recent issues of MSDN magazine). Is this because the debugger in Visual Studio is good enough? Any opinions and advice will be greatly appreciated. Thanks very much, Sean
BoundsChecker, Purify and other diagnostic tools solve slightly different problems than built-in debugger in VC6. They are used for pinpointing errors like memory/resource leaks and invalid parameters passed to Windows API. The built-in debugger is for watching stack/variables/memory etc. Sure, there's some leak detection built into C/C++ runtime, but it's a basic level only. I've used both BoundsChecker and Purify - and Purify is my favorite program. However, I think you should check it yourself before spending hard-earned cash. Both programs have free evaluation versions on the web. Tomasz Sowinski -- http://www.shooltz.com
-
The debugger in VC6 is pretty decent (I wish it would expand macros and reveal the value of constants). Boundschecker sometimes falsely identifies memory leaks, but is good at pointing out where leaks might be occurring in other code (Stingray libraries for instance). It's a good add-on, but I only use it as a last resort, and as a last resort tool, I don't see it was being worth the relatively excessively high price. To hell with those thin-skinned pillow-biters. - Me, 10/03/2001
We used BC for quite a while as a 'final check' of the code, but we no longer use it because of the excessive upgrade costs - each new version is an expensive addition, and the features have changed very little. Since BC 5 doesn't integrate with VC 6, we no longer use it. ----------------------- The sermon on the mount... Man 1 : Hear that? Blessed are the greek. Man 2 : The greek? Man 1 : Well apparently, he's going to inherit the earth. Man 2 : Did anyone catch his name?
-
Hi All, I am considering getting a Windows debug tool such as BoundsChecker (the only such program that I am even a little familiar with). I am looking for opinions on the usefulness of these tools, and specific recommendations for products. Who are BoundsChecker's competitors? I seem to recall a tool called Purify, but can' really think of much else. It seems like the market for these tools is diminishing (there aren't even any adds for debuggers in recent issues of MSDN magazine). Is this because the debugger in Visual Studio is good enough? Any opinions and advice will be greatly appreciated. Thanks very much, Sean
