[Python-Dev] make test failing in a spectacular way intest_codeccallbacks (original) (raw)

Tim Peters tim.one at comcast.net
Sun Dec 21 20:07:59 EST 2003

[Skip]

Fresh cvs up (no local changes) on Mac OS X 10.2.8 yields this while running testcodeccallbacks (non-framework build, configured only using --with-pydebug): ... Anyone else seen this?

Just tried on Windows. test_codeccallbacks crashes here in release or debug builds. Here from a debug build:

C:\Code\python\PCbuild>python_d ../lib/test/test_codeccallbacks.py test_backslashescape (main.CodecCallbackTest) ... ok test_badandgoodbackslashreplaceexceptions (main.CodecCallbackTest) ... ok test_badandgoodignoreexceptions (main.CodecCallbackTest) ... ok test_badandgoodreplaceexceptions (main.CodecCallbackTest) ... ok test_badandgoodstrictexceptions (main.CodecCallbackTest) ... ok test_badandgoodxmlcharrefreplaceexceptions (main.CodecCallbackTest) ... ok test_badhandlerresults (main.CodecCallbackTest) ... ok test_badregistercall (main.CodecCallbackTest) ... ok test_bug828737 (main.CodecCallbackTest) ... ok test_callbacks (main.CodecCallbackTest) ... ok test_charmapencode (main.CodecCallbackTest) ... ok test_decodehelper (main.CodecCallbackTest) ... ok test_encodehelper (main.CodecCallbackTest) ... ok test_longstrings (main.CodecCallbackTest) ... C:\Code\python\PCbuild>python_d ../lib/test/test_codeccallbacks.py test_backslashescape (main.CodecCallbackTest) ... ok test_badandgoodbackslashreplaceexceptions (main.CodecCallbackTest) ... ok test_badandgoodignoreexceptions (main.CodecCallbackTest) ... ok test_badandgoodreplaceexceptions (main.CodecCallbackTest) ... ok test_badandgoodstrictexceptions (main.CodecCallbackTest) ... ok test_badandgoodxmlcharrefreplaceexceptions (main.CodecCallbackTest) ... ok test_badhandlerresults (main.CodecCallbackTest) ... ok test_badregistercall (main.CodecCallbackTest) ... ok test_bug828737 (main.CodecCallbackTest) ... ok test_callbacks (main.CodecCallbackTest) ... ok test_charmapencode (main.CodecCallbackTest) ... ok test_decodehelper (main.CodecCallbackTest) ... ok test_encodehelper (main.CodecCallbackTest) ... ok test_longstrings (main.CodecCallbackTest) ...

and at that point it dies with a segfault. It's really hosed at that point -- I can't get into the debugger. If I start the test under the debugger, the debugger craps out. So no easy clues from me either.

Just to cheer things up , the bsddb3 tests are in much worse shape now on Win98SE than they are in 2.3.3 (about 50 more errors under current CVS).

I expect that 2.3.3 will be the last Python release .

BTW, when I cvs up'ed and recompiled to run the above, the only file I noticed getting recompiled was unicodeobject.c.

More information about the Python-Dev mailing list