delorie.com/archives/browse.cgi | search |
From: | Mark Phillips <umphill5 AT cs DOT umanitoba DOT ca> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Memory problem. |
Date: | Sat, 17 Jul 1999 16:14:40 -0500 |
Organization: | The University of Manitoba |
Lines: | 21 |
Message-ID: | <Pine.SUN.3.96.990717161027.17136A-100000@silver.cs.umanitoba.ca> |
NNTP-Posting-Host: | silver.cs.umanitoba.ca |
Mime-Version: | 1.0 |
X-Trace: | canopus.cc.umanitoba.ca 932246086 28845 130.179.24.6 (17 Jul 1999 21:14:46 GMT) |
X-Complaints-To: | Postmaster AT cc DOT umanitoba DOT ca |
NNTP-Posting-Date: | 17 Jul 1999 21:14:46 GMT |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Ok here's the deal. At one point in my program I do this: menu_bar = new menubar[foo]; menu_bar then points to the memory at address 0x710e0. A while later I do: temp2 = new char[bar]; temp2 then also points to the memory at address 0x710e0. This is bad since I still need menu_bar and I am fairly confident my program didn't `delete' the memory it uses. Is there any way this could have happened if I didn't `delete' the memory at 0x710e0 or must I have??? Also- is there any way to use the rhide debugger so that it will break whenever memory at that location is deallocated? Thanks. Mark
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |