Re: Track down SIGABRT

Subject	Re: Track down SIGABRT
From	Israel Brewster <israel@ravnalaska.net>
Date	2015-01-13 08:34 -0900
References	<B967FFA3-810A-4C9F-A353-A3C5E8C9ED6B@ravnalaska.net> <7FF67692-9F7B-4EE1-AD9F-83DAC545A78A@mac.com> <41D1FC10-000B-4DD7-8C40-12D92F62BC25@ravnalaska.net> <CANc-5Uzi-0XSJzAMQecNDwdi6RAr7cfj5-vT1-9b5PKsoJW+LQ@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.17688.1421170470.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Jan 13, 2015, at 8:26 AM, Skip Montanaro <skip.montanaro@gmail.com> wrote:

> Assuming you have gdb available, you should be able to attach to the
> running process, then set a breakpoint in relevant functions (like
> exit() or abort()). Once there, you can pick through the C stack
> manually (kind of tedious) or use the gdbinit file which comes with
> Python to get a Python stack trace (much less tedious, once you've
> made sure any version dependencies have been eliminated). Or, with the
> latest versions of gdb (7.x I think), you get more stuff built into
> gdb itself.
> 
> More details here:
> 
> https://wiki.python.org/moin/DebuggingWithGdb

Thanks, I'll look into that. Hopefully running with the debugger attached won't slow things down to much. The main thing I think will be getting the python extensions installed - the instructions only talk about doing this for linux packages.

> 
> Skip

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

Thread

Re: Track down SIGABRT Israel Brewster <israel@ravnalaska.net> - 2015-01-13 08:34 -0900

csiph-web