Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Helmut Giese Newsgroups: comp.arch.embedded Subject: A TclOO debug question Date: Thu, 31 Jul 2025 22:15:10 +0200 Organization: ratiosoft Lines: 18 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Date: Thu, 31 Jul 2025 20:15:12 +0000 (UTC) Injection-Info: dont-email.me; posting-host="ac48118423c1eb7c8de97dda4514832f"; logging-data="19125"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/2+nCGbgs3V2U75WeupKOw" Cancel-Lock: sha1:LHemKS428HlEPjvVWf0who5Sd3o= X-Newsreader: Forte Free Agent 1.93/32.576 English (American) Xref: csiph.com comp.arch.embedded:32442 Hello out there, I have a problem following the 'next' chain of an object hierarchy. More precisely: When destroying an object I destroy each of its children as well as all the objects it has acquired. So far so good - I can even follow (via 'puts') all destructor calls. But then an already destroyed object wants to destroy itself again although I have seen already its destructor message. In the stack trace I only see a chain like . . . The '.' being presumeably the 'next' calls. Question: Is there a way to find out whose 'next' call is hiding behind those '.' messages? Any help or idea will be greatly appreciated Helmut