Given that its failing on a call to libc I would do a quick run with
strace and ltrace.
(In your case ltrace will be probably be more useful.) You will be
able to see the calls into the libraries and you should see
if your segfault is inside expat or not. (ltrace output will be very long ;-)
On Fri, Apr 2, 2010 at 11:29 AM, Martin Aspeli <optilude+li...@gmail.com> wrote:
> Marius Gedminas wrote:
>> On Thu, Apr 01, 2010 at 06:07:26PM +0800, Martin Aspeli wrote:
>>> I'm not sure if this is a Python issue or a zope issue. We're getting a
>>> segfault on 64-bit SuSE Linux (SLES 11), originating from
>>> z3c.autoinclude, which in turn called zope.configuration's<include />
>>> implementation. This calls expat, which then crashes (no error, log
>>> message, or core file, but it has all the markings of a segfault) during
>>> parsing of the file.
>> On recent Ubuntu versions segfaults get recorded in dmesg and end up in
>> /var/log/kern.log like this:
>> Mar 22 02:10:03 fridge kernel: [7804719.781375] python: segfault at
>> 7fff84a7c000 ip 00007fff83aae7cb sp 00007fff84a7bd98 error 7 in
>> I assume that's a standard kernel feature now (we've 2.6.28, x86_64).
> Interesting. I'll check.
>>> The weird thing is that it's not parsing of any file: it happens during
>>> a standard configure.zcml (for the collective.xdv package), but
>>> z3c.autoinclude itself is invoked from another ZCML file, so it must've
>>> been able to read that.
>>> Any tips on how to debug or similar experiences would be appreciated!
>> Can you reproduce this, reliably?
>> I'd be reaching for python/expat debug symbols and gdb, probably.
> I'm not sure how to do that. My gdb fu is *very* limited. I also assume
> I'd need to re-build python and/or expat for this?
> Zope-Dev maillist - zope-...@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> https://mail.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -