➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: illegal use of malloc/free
Type: Stage:
Components: Interpreter Core Versions: Python 2.2
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: nnorwitz Nosy List: gurra-g, gvanrossum, nnorwitz, tim.peters
Priority: normal Keywords:

Created on 2002-05-17 00:31 by gurra-g, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Messages (5)
msg10831 - (view) Author: Gustav H�llberg (gurra-g) Date: 2002-05-17 00:31 
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.
msg10832 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2002-05-17 01:19 
Logged In: YES 
user_id=31435

Just noting that current CVS already uses PyMem_ in 
com_factor.
msg10833 - (view) Author: Gustav H�llberg (gurra-g) Date: 2002-05-17 10:46 
Logged In: YES 
user_id=546849

Ah, that should definitely be backported to releasebranches.
msg10834 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2002-06-05 18:40 
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.
msg10835 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2002-08-11 15:42 
Logged In: YES 
user_id=33168

Checked in as Python/compile.c 2.234.4.4.
History
Date User Action Args
2022-04-10 16:05:19adminsetgithub: 36612
2002-05-17 00:31:46gurra-gcreate