Home > C,C++ > Debugging


Related Categories

Debugging C++  
This chapter describes how dbx handles C++ exceptions and debugging C++ templates, including a summary of commands used when completing these tasks and examples with code samples. It is organized into the following sections: Using dbx with C++, Exception Handling in dbx, Debugging With C++ Templates, Command Reference.
Submitted: Feb 13, 2000
Debugging in C++  
In this lab we'll get away from VisualWorks for a while and try playing with C++. Hopefully, after doing this lab you'll have a better feel for the C++ language in general; the relationship between C++ and Smalltalk; how to code in C++; how to compile and run a C++ program. The procedure is pretty simple. Save the buggy C++ source code and call it library.cc just so that we can refer to it by that name throughout this document. Then open up a UNIX shell window on your workstation. You will use it to compile (and maybe edit) the program.
Submitted: Feb 13, 2000
KAI C++ Debugger  
The KAI C++ Debugger is an entirely new debugger, designed and implemented specifically for C++ programming, providing access to C++ features directly. Debugging a C++ program as if it was a C program is a thing of the past with the KAI C++ Debugger. The KAI C++ Debugger handles any ISO Standard C++ program compiled by KAI C++ in a uniform manner across all supported platforms. Learning a new debugger when you move from platform to platform is a thing of the past with the KAI C++ Debugger. The KAI C++ Debugger has a simple GUI interface that simplifies many ordinary debugging tasks.
Submitted: Feb 14, 2000
A First Look at C++ Program Analyzers  
C++ has a well-deserved reputation for power and flexibility. It has an equally well-deserved reputation for complexity; its gotchas are legion. For example, omitting a virtual destructor in a base class typically leads to incomplete destruction of derived class objects when they are deleted through base class pointers. Experienced C++ programmers learn to avoid these kinds of problematic constructs, but experience should not really be necessary: troublesome C++ can often be detected by static analysis, i.e., by tools that parse and analyze C++ source code. Such tools are becoming widely available, and during the summer and fall of 1996, we undertook an investigation to identify these tools and to assess their capabilities. In this article, we summarize the initial results of our investigation.
Submitted: Jan 11, 2000
Debugging and Tuning  
If debugging a service were simply a matter of setting a few breakpoints and hitting F5, like you would for a normal executable, there wouldn't be much to talk about on the topic. We've all used Visual C++'s interactive debugger, and by now we're probably experts at doing so. Unfortunately, that experience is not going to be much help here. In this chapter will be shown you a number of different techniques that you can use to work around these problems, and then focus on some more general issues that can help to keep you out of trouble in the first place.
Submitted: Feb 14, 2000
The ArrayDebugView-Add-In extends Visual Studio and adds graphical view capabilities to the C/C++-debugger. You can plot the data from any array by specifying a pointer expression and a length. Features: Zoom-function, a cursor, saving to a file, support for all complex numbers and stride. (Licence: GNU GPL)
Submitted: Nov 11, 2002
Debugging Programs in Pascal, C, C++ and Fortran  
It's not uncommon for over 50% of programming time to be spent of debugging. This document looks at various techniques and utilities (particularly wdb) that aid debugging. It will be useful to you if your program compiles but doesn't do what you expect when you run it.
Submitted: Feb 13, 2000
The D-Lib library provides a set of easy-to-use but powerful and easily configurable tools to perform a C/C++ programmer's daily debug as well as diagnostics needed by a system tester/maintainer. In fact the use of the D-Lib library gives very flexible debug printing with both compile-time and run-time management and also possibility to turn on/off (even run-time) some pieces of code without any recompilation. You can download from this site the sources, documentation and test/demo sources.
Submitted: Nov 28, 1999
EDM/2 - Debugging Classes in Borland C++  
When using Borland C++ for OS/2 I quickly found out that there are certain problems involved when debugging programs. Several of these were related to my programs, several were of a nature general to debugging and some were and are very specific problems due to Borland's debugger. The second type of problems manifested themselves in a context of Murphy's law: Everything goes wrong when you expect it the least, meaning your program has a fault especially when you are not debugging it. The third category meant that when debugging rather often, not only my program would crash but also the debugger.
Submitted: Feb 13, 2000
ABSTRACTS: Sixth USENIX C++ Conference  
Most debuggers do not support an object-oriented debugging model. A debugger should be able to provide the view that each object is an independent entity with its own breakpoint behavior. We also would like the debugger to plant a breakpoint on the "right" member function when a polymorphic identifier is involved. The technology used in most C++ implementations does not support these features as well as the rich run-time environments commonly provided for symbolic languages. This paper introduces the need for such constructs, and presents algorithms that can be used to implement them in the framework of common symbolic debuggers.
Submitted: Feb 13, 2000

  Privacy - Trademarks - Feedback - Terms of Use Copyright The MathWorks, Inc.