Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.albasani.net!news.stack.nl!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <rosuav@gmail.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.069
X-Spam-Evidence: '*H*': 0.86; '*S*': 0.00; 'explicitly': 0.05; 'debugging': 0.07; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'problem!': 0.16; 'scope.': 0.16; 'wrote:': 0.18; 'bit': 0.19; 'stack': 0.19; 'to:name:python-list@python.org': 0.22; 'least': 0.26; 'header:In-Reply-To:1': 0.27; 'generally': 0.29; 'message-id:@mail.gmail.com': 0.30; 'getting': 0.31; 'easier': 0.31; 'run': 0.32; 'fri,': 0.33; 'something': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'subject:?': 0.36; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'to:addr:python.org': 0.39; 'either': 0.39; 'called': 0.40; 'break': 0.61; "you're": 0.61; 'first': 0.61; "you'll": 0.62; 'soon': 0.63; 'more': 0.64; 'isolate': 0.84; 'off,': 0.84
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HZV3DAaadjl8uXpU+d7hkUQLG1tBnam74GXbkFGwVSQ=; b=HGwEq3MZodMAL+czsVu2gcCwixFPu0LcddoDjaynBNDPePfC2MIYjYhbo4s03yoQ4k 8RcuCAFRiGm4RwB/xaCCH3EJ5S7qgH+v3sXQHJcS/SI0YtnpLfQ5gYKmMp14wP2WuPuG 9EzBwv+t9ChT/dIF1f3KD7vG5JLI4IpgTuvnMhcO5UJc2MbT0DL7WTHqiOr9B3r5eTIV OjMc0jUxAzpYY/R87ICitobECnJnSUT5DmwMqyBYsMqcIga6POCqp9Dtq5TzMX9mKAXF DlhUeyo7W1HOgASNGDdLVtIFszxnXDKJkA5f/UbLBciNQ74yW97jTl+uca7XS0rYAWzV +HMQ==
MIME-Version: 1.0
X-Received: by 10.221.4.66 with SMTP id ob2mr1709953vcb.28.1402021825843; Thu, 05 Jun 2014 19:30:25 -0700 (PDT)
In-Reply-To: <87wqcuu6jd.fsf@vostro.rath.org>
References: <87fvjlv22v.fsf@vostro.rath.org> <CAPTjJmqzgZnziz3+yZb-4bsYtfxT2AG5HQ9Pb3Ya8AWDW8+oHA@mail.gmail.com> <87oay8pobi.fsf@rath.org> <87r433ri00.fsf@handshake.de> <87wqcuu6jd.fsf@vostro.rath.org>
Date: Fri, 6 Jun 2014 12:30:25 +1000
Subject: Re: Missing stack frames?
From: Chris Angelico <rosuav@gmail.com>
To: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.10802.1402021828.18130.python-list@python.org>
Lines: 12
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1402021828 news.xs4all.nl 2934 [2001:888:2000:d::a6]:52105
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:72810

On Fri, Jun 6, 2014 at 12:16 PM, Nikolaus Rath <Nikolaus@rath.org> wrote:
>  - Is there some way to make the call stack for destructors less confusing?

First off, either don't have refloops, or explicitly break them.
That'll at least make things a bit more predictable; in CPython,
you'll generally see destructors called as soon as something goes out
of scope. Secondly, avoid threads when you're debugging a problem! I
said this right at the beginning. If you run into problems, the first
thing to do is isolate the system down to a single thread. Debugging
is way easier without threads getting in each other's ways.

ChrisA