[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Sat Sep 25 09:37:58 2004 -->
- <!--x-from-r13: wbuazvyyf ng fcrnxrnfl.arg (Xbua [vyyf) -->
- <!--x-message-id: Pine.LNX.4.44.0409250825301.14536-[email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] C++ Debuggery and the Path of Destruction -->
- <li><em>date</em>: Sat Sep 25 09:37:58 2004</li>
- <li><em>from</em>: johnmills at speakeasy.net (John Mills)</li>
- <li><em>in-reply-to</em>: <<a href="msg00849.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] C++ Debuggery and the Path of Destruction</li>
Thanks for the help. I think I have enough guidance to rework my code,
instrument it to see what's going on, and minimize the chance of doing
this again.
On Sat, 25 Sep 2004, Geoffrey wrote:
> Bjorn Dittmer-Roche wrote:
> > On Fri, 24 Sep 2004, Barry Rountree wrote:
...
> >> __FILE__::__LINE__ is now creating a __WHATEVER__, address 0xabcddcab
> >> __FILE__::__LINE__ is now deleting a __WHATEVER__, address 0xabcddcab
...
> Excellent points both. What we used to do when we were oft times
> allocating memory in many section of code is add some #ifdefs to track
> allocation and freeing. Start the output with the memory address so
> that one can simply pipe the output to sort and should see matching
> allocations/frees:
>
> 804845c : allocated, foo.c(345)
> 804845c : freed, foo.c(345)
I might name the specific function, as line numbers change freely.
> The form is:
> address : [allocated|freed], __FILE__(__LINE__)
> We used #ifdef because we learned that about the time you had it all
> figured out and removed the debug code, you started having another
> memory leak. :)
Yes - I already have a couple of symbols to selectively print debug data
for different functions of the code.
Again, thanks to all contributors.
- John Mills
john.m.mills at alum.mit.edu
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00854" href="msg00854.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00849" href="msg00849.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00851.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00853.html">[ale] Linux Ext2 Unformat?</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00849.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00854.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00852"><strong>Date</strong></a></li>
<li><a href="threads.html#00852"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>