Problem with dyld_shared_cache

[Robert Peirce]

It seems like every day now I get the following error message on the
terminal:

dyld: shared cached file was build against a different libSystem.dylib,
ignoring cache
dyld: shared cached file was build against a different libSystem.dylib,
ignoring cache
dyld: shared cached file was build against a different libSystem.dylib,
ignoring cache

When I rebuild the cache the first time I get:

update_dyld_shared_cache[56314] current i386 cache file invalid because
/System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/
A/DesktopServicesPriv has changed
update_dyld_shared_cache[56314] current ppc cache file invalid because
/System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/
A/DesktopServicesPriv has changed
update_dyld_shared_cache[56314] current x86_64 cache file invalid
because
/System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/
A/DesktopServicesPriv has changed

I do it again and get no errors.

This is something new. My computer is four years old and this has just
started since I lost my mach_kernel and sym links in /.

I think I may have needed to do something beyond restoring mach_kernel
and the sym links but I don't know what.

[Robert Peirce]

In article <bob-***@5ad64b5e.bb.sky.com>,
Robert Peirce <***@peirce-family.com> wrote:

According to the man page for update_dyld_shared_cache, booting in safe
mode will clear the cache. I assume a normal boot thereafter will
rebuild it. If so, I may be okay.

I am also re-downloading the 10.6.7 combo and if the problem persists I
will try re-installing that.

I would still like to know what I may have missed when restoring the
mach_kernel and the symbolic links after I lost them. I must have lost
something else as well.

[Robert Peirce]

Post by Robert Peirce
I am also re-downloading the 10.6.7 combo and if the problem persists I
will try re-installing that.
I would still like to know what I may have missed when restoring the
mach_kernel and the symbolic links after I lost them. I must have lost
something else as well.

Turns out I had saved the original download. I re-installed it and so
far, so good. I would still like to know what I missed.

[Chris Ridd]

Post by Robert Peirce

Post by Robert Peirce
I am also re-downloading the 10.6.7 combo and if the problem persists I
will try re-installing that.
I would still like to know what I may have missed when restoring the
mach_kernel and the symbolic links after I lost them. I must have lost
something else as well.

Turns out I had saved the original download. I re-installed it and so
far, so good. I would still like to know what I missed.

There's no way to tell except by looking at backups taken before and
after the damage.

If you have these in Time Machine then you can use diff. Find the
directory on your TM disk containing all the dated snapshots:

cd "/Volumes/Time Machine/Backups.backupdb/Macintosh/"
[change "Time Machine" and "Macintosh" appropriately]

Then pick two snapshots and diff them:

diff -r --brief 2011-05-11-061610 2011-05-12-054843
[possibly lots of output]

If you haven't used Time Machine you could probably use diff that way
on a whole disk clone and the damaged disk.

[Robert Peirce]

Post by Robert Peirce
Turns out I had saved the original download. I re-installed it and so
far, so good. I would still like to know what I missed.

I reinstalled the 10.6.7 combo and it worked fine for two days. Then
the error message cropped up again. Something is messing with the
cache, but I have no idea what.

I don't think diffing the whole drive will help because there will be
too many differences and I won't know which are which!

Since re-installing helped for a while, I am doing that again.

[Robert Peirce]

Post by Robert Peirce

Post by Robert Peirce
Turns out I had saved the original download. I re-installed it and so
far, so good. I would still like to know what I missed.

I reinstalled the 10.6.7 combo and it worked fine for two days. Then
the error message cropped up again. Something is messing with the
cache, but I have no idea what.
Since re-installing helped for a while, I am doing that again.

That didn't last long, about 13 hours. I checked the console log to see
if I could identify anything starting the problem.

I'm not sure I understand the Date & Time entry. It appears it refers
to the time when the action starts rather than when it completes. At
any rate, here are the log entries for just before and just after the
problem starts. It appears to start right after launchd finishes
starting up. Could launchd be causing this problem, and if so, what
should I do about it? I ran cmp on a saved version from 4/25/11 and it
is identical to the current version so the program itself isn't the
problem.

5/25/11 10:00:29 AM kernel [Bluetooth::CSRHIDTransition] transition
complete.
5/25/11 10:00:29 AM kernel
CSRUSBBluetoothHCIController::setupHardware super returned 0
5/25/11 10:00:20 AM com.apple.launchd[1] *** launchd[1] has started up.
***
5/25/11 10:00:29 AM com.apple.kextd[10] dyld: shared cached file was
build against a different libSystem.dylib, ignoring cache
5/25/11 10:00:29 AM com.apple.DirectoryServices[11] dyld: shared
cached file was build against a different libSystem.dylib, ignoring cache

[Robert Peirce]

Post by Robert Peirce

Post by Robert Peirce

Post by Robert Peirce
Turns out I had saved the original download. I re-installed it and so
far, so good. I would still like to know what I missed.

I reinstalled the 10.6.7 combo and it worked fine for two days. Then
the error message cropped up again. Something is messing with the
cache, but I have no idea what.
Since re-installing helped for a while, I am doing that again.

That didn't last long, about 13 hours. I checked the console log to see
if I could identify anything starting the problem.
I'm not sure I understand the Date & Time entry. It appears it refers
to the time when the action starts rather than when it completes. At
any rate, here are the log entries for just before and just after the
problem starts. It appears to start right after launchd finishes
starting up. Could launchd be causing this problem, and if so, what
should I do about it? I ran cmp on a saved version from 4/25/11 and it
is identical to the current version so the program itself isn't the
problem.
5/25/11 10:00:29 AM kernel [Bluetooth::CSRHIDTransition] transition
complete.
5/25/11 10:00:29 AM kernel
CSRUSBBluetoothHCIController::setupHardware super returned 0
5/25/11 10:00:20 AM com.apple.launchd[1] *** launchd[1] has started up.
***
5/25/11 10:00:29 AM com.apple.kextd[10] dyld: shared cached file was
build against a different libSystem.dylib, ignoring cache
5/25/11 10:00:29 AM com.apple.DirectoryServices[11] dyld: shared
cached file was build against a different libSystem.dylib, ignoring cache

This may or may not be important. The error message only shows up in
Terminal.app. It may be that only Terminal.app is capable of displaying
the message or that only programs that might be called from the terminal
are affected by dyld problems.

[David Empson]

Post by Robert Peirce

Post by Robert Peirce

Post by Robert Peirce

Post by Robert Peirce
Turns out I had saved the original download. I re-installed it and so
far, so good. I would still like to know what I missed.

I reinstalled the 10.6.7 combo and it worked fine for two days. Then
the error message cropped up again. Something is messing with the
cache, but I have no idea what.
Since re-installing helped for a while, I am doing that again.

That didn't last long, about 13 hours. I checked the console log to see
if I could identify anything starting the problem.
I'm not sure I understand the Date & Time entry. It appears it refers
to the time when the action starts rather than when it completes. At
any rate, here are the log entries for just before and just after the
problem starts. It appears to start right after launchd finishes
starting up. Could launchd be causing this problem, and if so, what
should I do about it? I ran cmp on a saved version from 4/25/11 and it
is identical to the current version so the program itself isn't the
problem.
5/25/11 10:00:29 AM kernel [Bluetooth::CSRHIDTransition] transition
complete.
5/25/11 10:00:29 AM kernel
CSRUSBBluetoothHCIController::setupHardware super returned 0
5/25/11 10:00:20 AM com.apple.launchd[1] *** launchd[1] has started up.
***
5/25/11 10:00:29 AM com.apple.kextd[10] dyld: shared cached file was
build against a different libSystem.dylib, ignoring cache
5/25/11 10:00:29 AM com.apple.DirectoryServices[11] dyld: shared
cached file was build against a different libSystem.dylib, ignoring cache

This may or may not be important. The error message only shows up in
Terminal.app. It may be that only Terminal.app is capable of displaying
the message or that only programs that might be called from the terminal
are affected by dyld problems.

Hi Robert. I don't have an answer for your problem but just wanted you
to know that you aren't talking to yourself. I'm still puzzled so far.

One question: exactly where is Terminal.app displaying these messages?
Terminal doesn't normally show anything resembling log messages (unless
you view a log file in the shell).

"launch[1] has started up" normally appears in /var/log/system.log and
in the Console log early in the startup sequence for Mac OS X. I found
one for my most recent restart (last night) but none apart from that.

I doubt that launchd has anything to do with your dyld shared cache
problem. launchd is a critical system component which is responsible for
launching everything. The timing of the dyld error message is just due
to kextd detecting the problem nine seconds after launchd happened to
start.

[Robert Peirce]

Safe boot didn't clear the problem. Once the 10.6.7 combo is
downloaded, I'll install that to see what happens.

[Robert Peirce]

So far, so good. I re-installed the 10.6.7 combo package and a couple
of programs that produced error messages before have not yet done so.
We'll see over the next few days.