[Python-bugs-list] [ python-Bugs-557028 ] illegal use of malloc/free
noreply@sourceforge.net
noreply@sourceforge.net
Sat, 06 Jul 2002 10:34:03 -0700
Bugs item #557028, was opened at 2002-05-17 00:31
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=557028&group_id=5470
Category: Parser/Compiler
Group: Python 2.2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Gustav Hållberg (gurra-g)
>Assigned to: Jeremy Hylton (jhylton)
Summary: illegal use of malloc/free
Initial Comment:
com_factor() in compiler.c uses malloc/free, but should
use PyMem_Malloc/_Free.
The use of malloc/free is fatal when one has changed
Python's allocators to use something else than
malloc/free since the stuff malloc:ed there can later
on be (attempted to be) freed through a call to PyMem_Free.
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2002-06-05 18:40
Message:
Logged In: YES
user_id=6380
Yup, should be backported.
But note that pymalloc is known to be buggy in 2.2.x, and
we're not going to fix that.
----------------------------------------------------------------------
Comment By: Gustav Hållberg (gurra-g)
Date: 2002-05-17 10:46
Message:
Logged In: YES
user_id=546849
Ah, that should definitely be backported to releasebranches.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2002-05-17 01:19
Message:
Logged In: YES
user_id=31435
Just noting that current CVS already uses PyMem_ in
com_factor.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=557028&group_id=5470