[no subject]

I'm debugging some C++ compiled with gcc-[2.96|3.3], using gdb-5.2 in a
RH-7.3 environment. One of my objects is segfaulting on destruction and
I'm having trouble tracking it down. In fact, when I back up the fatal
stack I find I'm in the destructor for an identical object which happens
to be in a different class!

$%#$@^!!!

Naturally, I got a bit too clever and am handing pointers to one object
whose targets were allocated in another, and the originator - not the user
- must do the destruction.  I may be tripping on something like this, but
I'm not finding where I jumped the rails.

Any suggestions how to track this self-administered wedgie down?

TIA.

 - 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="00844" href="msg00844.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
<ul><li><em>From:</em> rountree at cs.uga.edu (Barry Rountree)</li></ul></li>
<li><strong><a name="00859" href="msg00859.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
<ul><li><em>From:</em> jknapka at kneuro.net (Joe Knapka)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00842.html">[ale] Linux Mail Server Recomendations</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00844.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00836.html">[ale] Re: [Prism54-users] Prism54.org - Apache 2</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00844.html">[ale] C++ Debuggery and the Path of Destruction</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00843"><strong>Date</strong></a></li>
<li><a href="threads.html#00843"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>