I think there's a way to enable heavier malloc debugging than the normal --with-pydebug. You'll have to enable it manually by editing Python.h I believe. Though it may already be on if you define Py_DEBUG. (Is WITH_PYMALLOC always on?) Ther may also be a libmalloc that enables heavier debugging; the malloc man page would have info.
On 9/7/07, Bill Janssen firstname.lastname@example.org wrote:
I've been expanding the SSL test suite, and found something like this cropping up, not always, but maybe 30% of the time. So I run it under gdb, but the "szone_error" breakpoint never gets hit. Any other malloc debugging tips I should know about?
(gdb) info break Num Type Disp Enb Address What 1 breakpoint keep y 0x900f2e56 <szone_error+6> (gdb) (gdb) run ./Lib/test/regrtest.py -R :4: -u all test_ssl Starting program: /local/python/trunk/src/python.exe ./Lib/test/regrtest.py -R :4: -u all test_ssl test_ssl [...] python.exe(22696,0xa000d000) malloc: *** error for object 0x650800: double free python.exe(22696,0xa000d000) malloc: *** set a breakpoint in szone_error to debug test test_ssl failed -- Traceback (most recent call last): File "/local/python/trunk/src/Lib/test/test_ssl.py", line 304, in testSSL3 CERTFILE2, CERTFILE3) File "/local/python/trunk/src/Lib/test/test_ssl.py", line 203, in serverParamsTest raise test_support.TestFailed("Unexpected SSL error: " + str(x)) TestFailed: Unexpected SSL error: (8, '_ssl.c:394: EOF occurred in violation of protocol')
1 test failed: test_ssl [23436 refs]
Program exited with code 01. (gdb)
Bill _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org