Kern protection failure

[nkuvu]

What translation? That made sense.

[BoA]

Now, in "English"...
Ok... What the display is telling you is: at memory location 0x00000009 there occurred an Executive Bad Access error of the type Kernel Protection Failure.

What this says is that code running from location 0x00000009 (or 10 byte past the start of memory) attempted to access memory that is protected from that access by the program current running. As a result, the Operating System's Executive is declaring an error and flushing the program as it is unable to meaningfully continue processing it.

In looking at the error again... the at value could be the address that the program was trying to access, rather than the program counter. This would make more sense but be somewhat less informative to a developer (IMHO). I haven't done enough code with OS X yet to have caused this specific error to occur... so, I haven't spent the time to learn the specifics of the syntax. But, in general context of writing code for Protected Operating Systems... I've seen the same type of error more times than I could ever hope to count. So, the general context I'm relating is valid...

[blb]

Quote:

BoA wrote:
...
In looking at the error again... the at value could be the address that the program was trying to access, rather than the program counter. This would make more sense but be somewhat less informative to a developer (IMHO). I haven't done enough code with OS X yet to have caused this specific error to occur... so, I haven't spent the time to learn the specifics of the syntax. But, in general context of writing code for Protected Operating Systems... I've seen the same type of error more times than I could ever hope to count. So, the general context I'm relating is valid...

This is correct, that value (0x09) is the address the program attempted to access. The useful information to a developer should show up later in the crash log; for example, if I try to access that address by telling printf() that there is a string there, I get the same error:

Quote:

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000009

Thread 0 Crashed:
#0 0x70000a50 in strlen
#1 0x70001b14 in vfprintf
#2 0x700129f0 in printf
#3 0x00001dec in main
#4 0x00001b38 in _start
#5 0x00001968 in start

(register information snipped)

When this occurs, is there ever anything consistent in the call stack (if it's readable like the one above, otherwise things are definitely more difficult)?

[TheAppleDoctor]

Well, earlier this evening I suddenly lost all privileges to all drives... and could not enable root to correct it. So.... right now I am running a bone-stock 10.1.5 with absolutely no software other than what Apple provided. No third-party drivers, no third-party anything (except for IE 5.2.1).

I will leave it like this, sucky as it is, for a few days, and see what happens.

Man, am I glad I back up to DVD! Nothing's gone, but I am going to hold off re-installing anything for a while. Crash log is now enabled, so if it does happen I will at least be able to show it to some of you guys that seem to understand it. (Not trying to be difficult, but I still don't understand even if you are talking about a physical problem with RAM, or what.)