[Python-Dev] make test failing in a spectacular way intest_codeccallbacks

[Tim Peters]

[Skip]
> Fresh cvs up (no local changes) on Mac OS X 10.2.8 yields this while
> running test_codeccallbacks (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 <wink>, 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 <wink>.

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