➜

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.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, belopolsky, cvs-src, meador.inge
Date 2013-06-10.10:13:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370859205.85.0.639598224585.issue18178@psf.upfronthosting.co.za>
In-reply-to
Content 
Said simpler: dlmalloc.c code is indeed compiled twice:
- once as part of closures.c, which #include "dlmalloc.c"; this is done carefully (with 'static' and 'USE_DL_PREFIX') to not clash with standard malloc functions.
- once as a separate target; without USE_DL_PREFIX it will define functions named malloc() and free()...

The second one is not necessary, of course. The patch looks good to me.
History
Date User Action Args
2013-06-10 10:13:25amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, belopolsky, meador.inge, cvs-src
2013-06-10 10:13:25amaury.forgeotdarcsetmessageid: <1370859205.85.0.639598224585.issue18178@psf.upfronthosting.co.za>
2013-06-10 10:13:25amaury.forgeotdarclinkissue18178 messages
2013-06-10 10:13:25amaury.forgeotdarccreate