[Zope-dev] Segfault in zope.configuration

[Marius Gedminas]

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[10447]: segfault at 7fff84a7c000 ip 00007fff83aae7cb sp 00007fff84a7bd98 error 7 in libc-2.9.so[7fff83a2b000+168000]

I assume that's a standard kernel feature now (we've 2.6.28, x86_64).

> 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.

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3 consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20100402/c44fab25/attachment.bin