> Adam Olsen <rhamph@gmail.com> added the comment:
> 
> I see no common symbols between #3102 and #3092, so unless I missed
> something, they shouldn't be involved.
> 
> I second the notion that multiprocessing's use of pickle is the
> triggering factor.  Registering so many types is ugly, and IMO it
> shouldn't register anything it doesn't control.  We should either
> register them global or not at all, and *never* as a side-effect of
> loading a separate module.
> 
> I do see some win32-specific behaviour, which may be broken.  Thomas,
> wanna try commenting out these two lines in sharedtypes.py:rebuild_ctype?
> 
>     if sys.platform == 'win32' and type_ not in copy_reg.dispatch_table:
>         copy_reg.pickle(type_, reduce_ctype)

This fixes the failure in test_ctypes, but test_multiprocessing no longer works:

c:\svn\trunk\PCbuild>.\\python_d  -E -tt ../lib/test/regrtest.py test_multiprocessing test_ctypes
test_multiprocessing
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "c:\svn\trunk\lib\multiprocessing\forking.py", line 297, in main
self = load(from_parent)
EOFError
[48274 refs]
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "c:\svn\trunk\lib\multiprocessing\forking.py", line 297, in main
self = load(from_parent)
EOFError
[48763 refs]
test test_multiprocessing failed -- errors occurred; run in verbose mode for details
test_ctypes
1 test OK.
1 test failed:
    test_multiprocessing
[118894 refs]

c:\svn\trunk\PCbuild>