home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- From: nikki@trmphrst.demon.co.uk (Nikki Locke)
- Path: sparky!uunet!pipex!demon!trmphrst.demon.co.uk!nikki
- Subject: Re: Microsoft C/C++ version 7 memory glitch
- Reply-To: nikki@trmphrst.demon.co.uk
- Distribution: world
- X-Mailer: cppnews $Revision: 1.20 $
- Organization: Trumphurst Ltd.
- Lines: 16
- Date: Thu, 5 Nov 1992 12:22:49 +0000
- Message-ID: <720991369snx@trmphrst.demon.co.uk>
- Sender: usenet@gate.demon.co.uk
-
- In article <92Nov02.183738.28361@acs.ucalgary.ca> gerke@acs.ucalgary.ca (Ken Gerke) writes:
- >
- > Someone brought in some C++ code to my office today that tries to
- > allocate the same chunk of memory twice. It just uses regular
- > calls to the 'new' function and is built with the medium memory
- > model. Trivial, seemingly unrelated changes make the problem
- > disappear, but don't give us a lot of confidence that the problem
- > has been solved. Anyone out there have a guess where to find a
- > more certain answer?
- Usually caused by freeing a pointer not allocated with malloc, or deleting
- a pointer not allocated with new, or using the wrong one of "delete []" and
- "delete". Try one of the debugging memory allocation packages about, which
- should point out the problem.
- --
- Nikki Locke,Trumphurst Ltd.(PC and Unix consultancy) nikki@trmphrst.demon.co.uk
- trmphrst.demon.co.uk is NOT affiliated with ANY other sites at demon.co.uk.
-