[Zope-dev] Segfault in zope.configuration

Marius Gedminas marius at gedmin.as
Fri Apr 2 09:07:32 EDT 2010


A: Because it destroys the flow of the conversation
Q: Why is it bad?
A: No, it's bad.
Q: Should I top post in replies to mailing lists?

On Fri, Apr 02, 2010 at 12:26:59PM +0800, Tim Hoffman wrote:
> Hi Martin
> 
> Given that its failing on a call to libc I would do a quick run with
> strace and ltrace.

That was my segfault, not Martin's.  I suspect hardware, as it's very
non-deterministic (a small pure-Python script that runs every 5 minutes
segfaults once in a few months).

> (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
> immediately
> 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+lists at 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[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).

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/24683a46/attachment.bin 


More information about the Zope-Dev mailing list