[EMAIL PROTECTED] wrote:
> Robin> Just replaced three PyMem_DEL's with PyObject_FREE and things now
> Robin> work again.
>
> Can you send me a patch?
>
> Thx,
>
> Skip
On its way
--
Robin Becker
--
http://mail.python.org/mailman/listinfo/python-list
Robin> Just replaced three PyMem_DEL's with PyObject_FREE and things now
Robin> work again.
Can you send me a patch?
Thx,
Skip
--
http://mail.python.org/mailman/listinfo/python-list
Steve Holden wrote:
> Robin Becker wrote:
...
>> Has anyone got any clue what the problem might be or a fixed version of the
>> code?
>
> I'm guessing this might be to do with the changes that have been made to
> enable 64-bit readiness in the code, but I couldn't suggest specifics.
>
> Sus
Robin Becker wrote:
> I have a segfault problem in Python2.5 RC1 (win32) when using the venerable
> extension sgmlop.c.
>
> In case that was just because our copy was very old I downloaded a later
> source
> from http://pyxml.cvs.sourceforge.net, but that code (version 1.14 loewis)
> still
>
Robin Becker wrote:
> I have a segfault problem in Python2.5 RC1 (win32) when using the venerable
> extension sgmlop.c.
..
> Has anyone got any clue what the problem might be or a fixed version of the
> code?
I think this is PyObject_NEW mixed with PyMem_DEL, I thought that had already
come
I have a segfault problem in Python2.5 RC1 (win32) when using the venerable
extension sgmlop.c.
In case that was just because our copy was very old I downloaded a later source
from http://pyxml.cvs.sourceforge.net, but that code (version 1.14 loewis)
still
suffers from this problem.
The probl
