Path: csiph.com!usenet.pasdenom.info!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.python
Subject: Re: Track down SIGABRT
Date: Tue, 13 Jan 2015 09:31:12 -0800
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <87h9vuoae7.fsf@jester.gateway.pace.com>
References: <B967FFA3-810A-4C9F-A353-A3C5E8C9ED6B@ravnalaska.net> <7FF67692-9F7B-4EE1-AD9F-83DAC545A78A@mac.com> <mailman.17686.1421168721.18130.python-list@python.org>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="cf2250d04a15656821738afa87e3379c"; logging-data="11273"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19JmnkvDO29U206bJT5LPqC"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:stOFRAXP4Dk8XckdGbqZwD0rfNk= sha1:rdNiF9y7t/Z+F+/mJcIZiYEzNDM=
Xref: csiph.com comp.lang.python:83712

Israel Brewster <israel@ravnalaska.net> writes:
>         when it again crashed with a SIGABRT. The crash dump the
>         system gave me doesn't tell me much, other than that it looks
>         like python is calling some C function when it crashes. I've
>         attached the crash report, in case it can mean something more
>         to someone else.

Somehow I missed the original post: did you get a core dump?  The
next thing to do is examine it under gdb.

>         
>         Can anyone give me some hints as to how to track down the
>         cause of this crash? 

If it's recurring, recompile python with -g to generate debugging
symbols, so you'll have an easier time examining the dump.  You can even
run the whole interpreter under gdb, though doing that for 33 days might
be uncharted territory.