Re: Missing stack frames?

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	2014-06-06 12:30 +1000
Subject	Re: Missing stack frames?
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.10802.1402021828.18130.python-list@python.org> (permalink)

Show all headers | View raw

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

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Missing stack frames? Chris Angelico <rosuav@gmail.com> - 2014-06-06 12:30 +1000

csiph-web