On Jul 17, 2008, at 6:22 PM, Mark Dickinson <report@bugs.python.org>  
wrote:

>
> New submission from Mark Dickinson <dickinsm@gmail.com>:
>
> As of revision 65077 of the trunk, I'm getting errors in
> test_multiprocessing that seem to point to memory corruption in object
> allocation/deallocation.  The failures are intermittent, and of a
> similar nature to the errors I was seeing previously, outlined in  
> issue
> 3088.
>
> The platform is OS X 10.5.4 (not a fresh install---it was an upgrade
> from OS X 10.4, in case this makes any difference), running on a  
> MacBook
> Pro.  I'm running a freshly checked out debug build of the trunk.
>
> Here's what I did:
>
> (1) make a fresh svn+ssh checkout of the trunk
> (2) ./configure --with-pydebug && make
> (3) ./python.exe Lib/test/test_multiprocessing.py
> (4) repeat step (3) until something nasty happens.
>
> The results vary from run to run, and 80-90% of the runs of
> test_multiprocessing pass.  Here are 3 of the failures I've seen,
> occurring on three separate runs of test_multiprocessing.
>

I am/was going to help you with this when you emailed me your last  
email - I'm disturbed none of my machines or the buildbots for that  
matter are seeing this. Can you post the output from:

Echo $LD_LIBRARY_PATH
which gcc
gcc -v