Logged In: YES 
user_id=580910

The scary bit is that the bug was "fixed" due to unclear differences between 
the build environment used for 2.5c1 and 2.5c2. 

I'll be building 2.5final as well, so expect this will stay fixed but I'm not 
entirely happy due to not knowing what caused the failure in the first place. It 
looks like 2.5c1 was build with a slighly different version of GCC (although 
both machines has Xcode 2.3 installed).

BTW. The issue still exists for 2.4.x, I hope to work on the 2.4 branch this 
weekend.