Built binary not updating

Question

Created Jul ’15

Replies 3

Boosts 0

Participants 2

Sorry, This is probibly not the right place to post this but i cannot find anywhere more suitable.

I have encountered a weird issue where after building a binary several times directly using clang it fails to update the run binary. A system reboot is needed for the binary that was actualy newly built to run, otherwise on OLD version runs everytime.

Like I said its a wierd hard to explain issue.

I get the feeling that its related to the caching of files in memory. Something like

1. File Write

˅

2. memory version of file

˅

3. File system

where after some time step 2 will be skipped for some unknown reason.

Only solution i Have found is to reboot.

Has anybody else experienced anything like this?

VLPokey

Answered by vlpokey in 48157022

Issue was caused by a failing HDD. After installing to and booting from a different HDD the problem has disspeared.

Its a little unsettling that no errors were presented in any way that hinted towards the failing HDD, due to that I suspect that a bug still exists.

As the original problem itself has been resolved i'm marking this as solved/correct.

Phillip.

Boost

Answer 1

DTS Engineer OP

Apple

Jul ’15

If you

rm

the original binary before building the new one, does that improve things?

Share and Enjoy
—
Quinn "The Eskimo!"
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 2

vlpokey OP

Jul ’15

Hi,

I did try that at one point yes, no improvement.

The weirdest time was when i deleted the binary from disk and was still able to run it in the terminal.

Unfortunately this issue seems to trigger very randomly and its not obvious when it does.

Phillip.

0

Answer 3

vlpokey OP

Sep ’15

Accepted Answer

Issue was caused by a failing HDD. After installing to and booting from a different HDD the problem has disspeared.

Its a little unsettling that no errors were presented in any way that hinted towards the failing HDD, due to that I suspect that a bug still exists.

As the original problem itself has been resolved i'm marking this as solved/correct.

Phillip.

0