On Tue, Apr 6, 2010 at 10:25 PM, Martin Aspeli optilude+li...@gmail.com wrote:
So this is still in pyexpat C code as far as I can tell. :-(
This is saddening.
I've not managed a 64-bit sandbox, which I suspect is what I really
need to debug that. Will shoot for this weekend, since last didn't
Fred Drake wrote:
On Tue, Apr 6, 2010 at 10:25 PM, Martin Aspelioptilude+li...@gmail.com
wrote:
So this is still in pyexpat C code as far as I can tell. :-(
This is saddening.
But on the other hand, your dedication in helping me find a fix is
heartening. ;)
I've not managed a 64-bit
On Wed, Apr 7, 2010 at 9:29 AM, Martin Aspeli optilude+li...@gmail.com wrote:
I have a slight suspicion that lxml is involved somewhere. I've managed
to make it crash reliably simply by doing a parse of an XML file, and I
think such a parse may be happening as a side effect of a module import
On Fri, 02 Apr 2010 11:29:06 +0800
Martin Aspeli optilude+li...@gmail.com wrote:
Hello,
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
Martin Aspeli wrote:
Hi,
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'sinclude /
implementation. This calls expat, which then crashes (no error, log
Martin Aspeli wrote:
At this point, something is printed to the console. collective.wtf is a
dependency of lw.portal, and its ZCML is being included from lw.portal.
/home/osc/osc/eggs/collective.wtf-1.0b9-py2.6.egg/collective/wtf/exportimport.py:8:
DeprecationWarning: InitializeClass is
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
On Fri, Apr 02, 2010 at 11:29:06AM +0800, Martin Aspeli wrote:
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.
Have you used pdb? gdb is mostly the same.
gdb python
and when it crashes, type 'bt' at the (gdb)
sorry
On Fri, Apr 2, 2010 at 9:07 PM, Marius Gedminas mar...@gedmin.as wrote:
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
Hi,
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,
On Thu, Apr 1, 2010 at 6:07 AM, Martin Aspeli optilude+li...@gmail.com wrote:
Any tips on how to debug or similar experiences would be appreciated!
If you're on some Unix flavor, you should be able to deconstruct the
return code from the runzope process to determine if the app was
killed by a
Fred Drake wrote:
On Thu, Apr 1, 2010 at 6:07 AM, Martin Aspelioptilude+li...@gmail.com
wrote:
Any tips on how to debug or similar experiences would be appreciated!
If you're on some Unix flavor, you should be able to deconstruct the
return code from the runzope process to determine if the
On Thu, Apr 1, 2010 at 7:29 AM, Martin Aspeli optilude+li...@gmail.com wrote:
I'm pretty sure it is. The pdb rabbit hole ended at pyexpat.c. I can't
see what's going on there, but when I did 'r' it blew up.
If you can point me at the ZCML file you were trying to parse (or
email it to me
Fred Drake wrote:
On Thu, Apr 1, 2010 at 7:29 AM, Martin Aspelioptilude+li...@gmail.com
wrote:
I'm pretty sure it is. The pdb rabbit hole ended at pyexpat.c. I can't
see what's going on there, but when I did 'r' it blew up.
If you can point me at the ZCML file you were trying to parse (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Fred Drake wrote:
On Thu, Apr 1, 2010 at 7:29 AM, Martin Aspelioptilude+li...@gmail.com
wrote:
I'm pretty sure it is. The pdb rabbit hole ended at pyexpat.c. I can't
see what's going on there, but when I did 'r' it blew up.
On Thu, Apr 1, 2010 at 2:17 PM, Tres Seaver tsea...@palladion.com wrote:
/me is deeply suspicious of *any* distro-provided python, ever.
I'm also suspicious of 64-bit builds, given that I'm not using one on
my dev machine.
I've picked up the OpenSuSE installation ISOs; hopefully that's close
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
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Fred Drake wrote:
On Thu, Apr 1, 2010 at 7:29 AM, Martin Aspelioptilude+li...@gmail.com
wrote:
I'm pretty sure it is. The pdb rabbit hole ended at pyexpat.c. I can't
see what's going on there, but
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'sinclude /
Fred Drake wrote:
On Thu, Apr 1, 2010 at 2:17 PM, Tres Seavertsea...@palladion.com wrote:
/me is deeply suspicious of *any* distro-provided python, ever.
I'm also suspicious of 64-bit builds, given that I'm not using one on
my dev machine.
I've picked up the OpenSuSE installation ISOs;
Hi Martin
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
immediately
if your segfault is inside expat or not. (ltrace output
21 matches
Mail list logo
