[Zope-dev] Core dumps - How to find out the bug?

[Anthony Baxter]

>>> =3D?iso-8859-1?Q?Dario_Lopez-K=3DE4sten?=3D wrote
> I only have core dumps to work from. I include the stack from latest co=
re
> dump.
> I am using python 2.1.2 (release), Zope2.4.3 release, RedHat Linux 7.2.=

> Python is compiled --without-pymalloc

Hm. The bug report you sent is pretty much exactly what I'd expect when
hitting the Python Compiler stacksize bug. I suspect the problem here is
that Zope 2.4.3 provides it's own complete copy of the Compiler, so you'r=
e
not seeing Jeremy's fixes. Possible solutions:

  - wait for Zope 2.4.4
  - upgrade to the current CVS version of the Zope 2.4 branch, Zope-2_4-b=
ranch.
  This contains what will become (hopefully, shortly) 2.4.4. I'm assuming=
 =

  there's a 2.4.4 planned.
  - upgrade to the current 2.5 beta.


> =

> -----
> #0  0x0806fb77 in subtract_refs (containers=3D0x80b228c) at
>     ./Modules/gcmodule.c:170
> #1  0x0806ff74 in collect (young=3D0x80b228c, old=3D0x80b2298) at
>     ./Modules/gcmodule.c:382
> #2  0x080701c2 in collect_generations () at
>     ./Modules/gcmodule.c:479

Anthony

-- =

Anthony Baxter     <anthony@interlink.com.au>   =

It's never too late to have a happy childhood.