home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!spool.mu.edu!sgiblab!sti!sti!not-for-mail
- From: westes@smurf.sti.com (Will Estes)
- Newsgroups: comp.lang.c++
- Subject: Re: Death of Borland C++ Compiler
- Date: 19 Dec 1992 13:00:35 -0800
- Organization: Mail Group
- Lines: 23
- Message-ID: <1h02hjINNn22@smurf.sti.com>
- References: <chaolin.88@fcit-m1.fcit.monash.edu.au> <BzH1LF.9yA@ais.org>
- NNTP-Posting-Host: smurf.sti.com
-
- In article <BzH1LF.9yA@ais.org> draper@ais.org (Patrick Draper) writes:
- >In your case, it sounds like you've got memory bugs. The fact that you're
- >using pointer->pointer->pointer type expressions indicates to me a hard to
- >debug program. The compiler shouldn't have any trouble with these, I've
- >never had these problems at all.
- >
- >Try using the 80386 debugger. It loads the program into the same memory
- >address as DOS does from the command line. Any location dependent errors
- >will show up as they do without the debugger.
-
- Chaolin, you may also want to get the MicroQuill product "SmartHeap For
- Windows". From what I understand it has some outstanding features to
- check for heap overwrites at run-time, as well as allowing you to use
- malloc() for memory calls without wasting memory handles (i.e.,
- SmartHeap does its own sub-allocation management of a single
- GlobalAlloc() memory area).
-
- We have just received the product and haven't started using it yet, but
- I hear good things from people who have used it. Comments from other
- users of this product are welcome.
-
- --
- Will Estes Internet: westes@netcom.com
-