Nu kan jag ingenting mer om detta än vad vem som helst kan googla sig till så ta vad jag skriver med en nypa salt.
Men:
Här har du apples tech note på hur en krasch logg ska tolkas:
https://developer.apple.com/library/...CCRASHLOGSTATE
I den kan vi se detta:
Kod:
Crashed Thread: 7
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Apples kommentar:
Citat:
The most common forms of exception are:
EXC_BAD_ACCESS/KERN_INVALID_ADDRESS — This is caused by the thread accessing unmapped memory. It may be triggered by either a data access or an instruction fetch; the Thread State section describes how to tell the difference.
Går vi till Thread State section ser vi:
Kod:
Thread 7 crashed with X86 Thread State (64-bit):
rax: 0x000000011dc998b0 rbx: 0x0000000100912c38 rcx: 0x00000001005de340 rdx: 0x0000000000105a60
rdi: 0x00000001005de340 rsi: 0x0000000100912c38 rbp: 0x0000000000000000 rsp: 0x000000010947e878
r8: 0x000000010020f880 r9: 0x000000010028e410 r10: 0x00000000fe7ed986 r11: 0x00000000af8da1e6
r12: 0x000000011db16490 r13: 0x000000010947eb6e r14: 0x0000000100c13440 r15: 0x0000000000000000
rip: 0x0000000000000000 rfl: 0x0000000000010202 cr2: 0x0000000000000000
Om detta säger Apple:
Citat:
Focus on two values: eip and the exception address (described earlier).
eip is the program counter at the time that the exception occurred. That is, it's the address of the instruction that caused the exception. For most non-memory access exceptions (for example, EXC_ARITHMETIC/EXC_I386_DIV caused by an integer division by zero), this is the key value.
For memory access exceptions:
If eip is equal to the exception address, the exception was caused by fetching instructions. Typically this means:
you've called a bogus function pointer (or, equivalently, called a method on a bogus object)
you've returned to a bad address which, in turn, means that you've corrupted the stack
If eip is not equal to the exception address, the exception was caused by a memory access instruction (in terms of C, this means that you're dereferencing an invalid pointer).
Samt:
Citat:
n general you should interpret this thread state in much the same way as you would a 32-bit Intel thread state. The key differences are:
The PC address is in rip, not eip.
Eftersom rip == exception address:
If eip is equal to the exception address, the exception was caused by fetching instructions. Typically this means:
you've called a bogus function pointer (or, equivalently, called a method on a bogus object)
you've returned to a bad address which, in turn, means that you've corrupted the stack
Och här tar det slut för mig, någon annan har kanske förmåga att analysera detta djupare.
Hittade denna tracken som liknar lite:
https://trac.videolan.org/vlc/ticket/11245
Men det gäller VLC 2.1.3 och du har 2.1.5 så det borde vara fixat.
