Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!goblin1!goblin.stu.neva.ru!uio.no!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.070 X-Spam-Evidence: '*H*': 0.86; '*S*': 0.00; 'explicitly': 0.05; 'preferred.': 0.05; 'debugging': 0.07; 'fingerprint:': 0.16; 'fruit': 0.16; 'gpg': 0.16; 'problem!': 0.16; 'scope.': 0.16; 'wrote:': 0.18; 'bit': 0.19; 'stack': 0.19; 'id:': 0.23; 'header :User-Agent:1': 0.23; 'case.': 0.24; 'example.': 0.24; 'least': 0.26; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; 'generally': 0.29; 'code': 0.31; 'getting': 0.31; 'easier': 0.31; 'apparently': 0.31; 'writes:': 0.31; 'run': 0.32; 'fri,': 0.33; 'guess': 0.33; 'actual': 0.34; 'something': 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; 'received:org': 0.40; 'called': 0.40; 'how': 0.40; 'even': 0.60; 'break': 0.61; 'simple': 0.61; "you're": 0.61; 'first': 0.61; "you'll": 0.62; 'soon': 0.63; 'more': 0.64; 'gotten': 0.74; 'flies': 0.84; 'isolate': 0.84; 'off,': 0.84; 'encrypted': 0.91 From: Nikolaus Rath To: python-list@python.org Subject: Re: Missing stack frames? References: <87fvjlv22v.fsf@vostro.rath.org> <87oay8pobi.fsf@rath.org> <87r433ri00.fsf@handshake.de> <87wqcuu6jd.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: python-list@python.org Date: Fri, 06 Jun 2014 19:04:03 -0700 In-Reply-To: (Chris Angelico's message of "Fri, 6 Jun 2014 12:30:25 +1000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 30 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1402106655 news.xs4all.nl 2831 [2001:888:2000:d::a6]:33157 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:72896 Chris Angelico writes: > On Fri, Jun 6, 2014 at 12:16 PM, Nikolaus Rath wrote: >> - Is there some way to make the call stack for destructors less confusi= ng? > > First off, either don't have refloops, or explicitly break them. The actual code isn't as simple as the example. I wasn't even aware there were any refloops. Guess I have to start hunting them down now. > 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. I don't see how this would have made a difference in this case. I still would have gotten lots of apparently non-sensical backtraces. Only this time they would all come from MainThread. Best, -Nikolaus --=20 GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB