Ned Deily added the comment: Further testing shows that the problem is not limited to OS X 10.8 or clang: a similar debug build attempt fails on OS X 10.6 with Apple gcc-4.2.
./configure --with-pydebug CC=gcc-4.2 MACOSX_DEPLOYMENT_TARGET=10.6 make gcc-4.2 -Wl,-stack_size,1000000 -framework CoreFoundation -o python.exe Modules/python.o libpython3.4dm.a -ldl -framework CoreFoundation ./python.exe -E -S -m sysconfig --generate-posix-vars Debug memory block at address p=0x100515a40: API 'm' 232 bytes originally requested The 7 pad bytes at p-7 are FORBIDDENBYTE, as expected. The 8 pad bytes at tail=0x100515b28 are FORBIDDENBYTE, as expected. The block was made by call #5440 to debug malloc/realloc. Data at p: 2f 00 00 00 75 00 00 00 ... 6e 00 00 00 00 00 00 00 Fatal Python error: bad ID: Allocated using API 'm', verified using API 'r' Current thread 0x00007fff70f4bcc0: make: *** [pybuilddir.txt] Abort trap ---------- title: Debug Python build fails on OS X with current clang: Fatal Python error: bad ID: Allocated using API 'm', verified using API 'r' -> Debug Python build fails on OS X: Fatal Python error: bad ID: Allocated using API 'm', verified using API 'r' _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18398> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com