From -3124435354168945777
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 109fba,4a83429e368029eb,start
X-Google-Attributes: gid109fba,public
X-Google-Thread: f78e5,4a83429e368029eb,start
X-Google-Attributes: gidf78e5,public
X-Google-ArrivalTime: 1993-09-12 12:10:19 PST
Xref: gmd.de comp.std.c++:3594 comp.lang.c++:31767
Path: gmd.de!newsserver.jvnc.net!howland.reston.ans.net!usc!usc!not-for-mail
From: aabdalla@pollux.usc.edu (AAA)
Newsgroups: comp.std.c++,comp.lang.c++
Subject: Memory, pointers debugger aid
Date: 12 Sep 1993 12:07:44 -0700
Organization: University of Southern California, Los Angeles, CA
Lines: 22
Sender: aabdalla@pollux.usc.edu
Message-ID: <26vs20$bdf@pollux.usc.edu>
NNTP-Posting-Host: pollux.usc.edu

Hi, in this relatively small C++ project I'm working on, some very random
wierd errors started occurring and it eventually turned out to be
accessing a function thru a NULL pointer.  Sigh.  Anyway, it was quite
difficult to track down, and *Deeper sigh* I just added a whole lot of
code to the project and similar symptoms started occurring.

So here's what I'm looking for: I read in a couple of programming 
magazines that there exists certain 'memory debuggers' which aid in 
the tracking down of array overflows, illegitimate pointer accesses 
(thru NULL pointers is what I definitely need), etc.  However, I've
never used any of these tools: can anyone recommend a particular tool
which meets my needs?

Also, are there any 'safe programming' techniques which are used to
avoid errors like this?  Short of switching to another language :-)

By the way, my platform: DOS on an IBM-compatible using Borland C++ 3.1

A big thanks.  Please send email.

AAA