Package: python Version: 2.7.13-2 Repro steps:
apt-get install python-pip python-dbg $ gdb --args python /usr/bin/pip install 'secp256k1>=0.13.1' GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from python...Reading symbols from /usr/lib/debug/.build-id/2e/a27a68b5bddba5a8e23fb91e7f5e464d6d864c.debug...done. done. (gdb) r Starting program: /usr/bin/python /usr/bin/pip install secp256k1\>=0.13.1 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Collecting secp256k1>=0.13.1 Using cached secp256k1-0.13.2-cp27-cp27mu-manylinux1_x86_64.whl Collecting cffi>=1.3.0 (from secp256k1>=0.13.1) Using cached cffi-1.9.1-cp27-cp27mu-manylinux1_x86_64.whl Collecting pycparser (from cffi>=1.3.0->secp256k1>=0.13.1) Installing collected packages: pycparser, cffi, secp256k1 Successfully installed cffi-1.9.1 pycparser-2.17 secp256k1-0.13.2 Program received signal SIGSEGV, Segmentation fault. 0x0000555555632974 in visit_decref () at ../Modules/gcmodule.c:360 360 ../Modules/gcmodule.c: No such file or directory. (gdb) bt #0 0x0000555555632974 in visit_decref () at ../Modules/gcmodule.c:360 #1 0x0000555555632a55 in dict_traverse () at ../Objects/dictobject.c:2144 #2 0x0000555555631c05 in subtract_refs () at ../Modules/gcmodule.c:385 #3 collect.lto_priv () at ../Modules/gcmodule.c:925 #4 0x000055555568c1e1 in PyGC_Collect () at ../Modules/gcmodule.c:1440 #5 0x000055555568b61e in Py_Finalize () at ../Python/pythonrun.c:448 #6 0x00005555556b0b38 in Py_Exit (sts=sts@entry=0) at ../Python/pythonrun.c:1783 #7 0x00005555556adfbd in handle_system_exit () at ../Python/pythonrun.c:1151 #8 0x00005555556ad8a6 in PyErr_PrintEx () at ../Python/pythonrun.c:1161 #9 0x00005555555b9cba in PyErr_Print () at ../Python/pythonrun.c:1064 #10 PyRun_SimpleFileExFlags (fp=<optimized out>, filename=<optimized out>, closeit=<optimized out>, flags=<optimized out>) at ../Python/pythonrun.c:952 #11 0x0000555555628af1 in Py_Main () at ../Modules/main.c:640 #12 0x00007ffff6f192b1 in __libc_start_main (main=0x555555628420 <main>, argc=4, argv=0x7fffffffea48, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffea38) at ../csu/libc-start.c:291 #13 0x000055555562831a in _start () It seems the pip install is completed and functional despite the crash. I've done just a few other pip installs and this does not happen for them. This is on an updated stretch system. Linux 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) x86_64 GNU/Linux
