The Debian (testing) version of Python2.7.11 does also exhibit the problem. I already told the Debian maintainer, Matthias Klose <[email protected]>, via email because I wanted to know exactly where he prefers to have it posted. He has already contributed here.
@Matthias: The issue remains open. Please advise on how I should proceed concerning Debian. In the mean time, I have attempted to narrow the debian/patches/* files down so I can find which patch produces the problem. But the patches quite heavily depend on each other, so I have not yet succeeded in producing a debianized build which does not have the problem. Still working at that. The bug can be traced in gdb by executing the testing setup, then saying "gdb ./zope-virtualenv/bin/python2.7-dbg" and in gdb: "run ./zope-virtualenv/bin/runzope -C ./zope-virtualenv/instance/etc/zope.conf". After sending the curl commands to produce the error, gdb exits with the above mentioned error: "Fatal Python error: ../Objects/descrobject.c:10 object at 0x1572240 has negative ref count -1 Program received signal SIGABRT, Aborted." Then the stack trace can be inspected. My knowledge of Python's memory management is not deep enough to really make any sense of what I'm seeing, other than it looks remotely like a "double free". I'll try to contribute more. Anyone with better understanding of Python internals, your help is much appreciated! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580577 Title: python2.7 crashes with SegFault when running Zope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
