toni magni - interoperability infrastructure actor
This is what happened:
I think what was going on was that OS 10.5 had recognized that on the internal boot drive there was something different than what was actually running in memory. Don't know why. Probably there is somewhere in the code a reference to the physical drive, instead of the mount point, or something like that. So it started rebuilding the dyld cache on the internal hard disk which was a 10.6. So we now had a 10.5 cache on 10.6 filesystem.
The easiest fix was deleting all /private/var/db/dyld/*cache*