segfault
full stack trace here:
http://paste.pound-python.org/show/2m3CI1LolgD4GGPOWhvU/
It seems like there might be a refcount issue.
Here's another. It looks similar to me.
http://paste.pound-python.org/show/axLWqRetbRnRklvXMdSi/
If you care to try to repro, i'm compiling this: https://github.com/bukzor/MySQLdb1
Using
$ echo $CC
/home/buck/trees/theirs/gcc-python-plugin/gcc-with-cpychecker --maxtrans=100000 --dump-json -wrapper gdb,--args
$ python setup.py build
(gdb) r
<segfault>
Ah this is python2.7-dbg on ubuntu trusty.
Notes to self: The first trace is happening during garbage-collection, whilst traversing a dict; the second one isn't during GC.
The first trace is in GC, specifically whilst visiting a value with key 'kind' (of a type that the pretty-printer treated as "unknown").
The 2nd trace is whilst looking up an entry within an OrderedDict, with key some gcc.VarDecl.
You mentioned on IRC that this happens only about 20% of the time.
Out of interest, which version of gcc?
Another: http://paste.pound-python.org/show/phqG6VimY5oaQhI12gY4/
It seems like there's a dict whose refcount is underflowing?
$ gcc --version
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Another http://paste.pound-python.org/show/se2RAMtH9iKmQtLXlFAp/
Here's another trace. http://paste.pound-python.org/show/5PXM8LoESmbBOyRQ8BSO/