[Python-bugs-list] [ python-Bugs-557028 ] illegal use of malloc/free

[noreply@sourceforge.net]

Bugs item #557028, was opened at 2002-05-16 20: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: Closed
Resolution: None
Priority: 5
Submitted By: Gustav Hållberg (gurra-g)
>Assigned to: Neal Norwitz (nnorwitz)
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: Neal Norwitz (nnorwitz)
Date: 2002-08-11 11:42

Message:
Logged In: YES 
user_id=33168

Checked in as Python/compile.c 2.234.4.4.

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2002-06-05 14: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 06: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-16 21: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