Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #83711 > unrolled thread

Re: Track down SIGABRT

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Track down SIGABRT Skip Montanaro <skip.montanaro@gmail.com> - 2015-01-13 11:26 -0600

#83711 — Re: Track down SIGABRT

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

Skip

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web