1. Forum
  2. Usenet
  3. UK.COMP.SYS.MAC

  • Re: Ping: Apd - Can you interpret a 'Crash Report'?

    From David Brooks@21:1/5 to Apd on Sun Jun 16 13:27:39 2024
    XPost: alt.computer.workshop

    On 16/06/2024 12:13, Apd wrote:
    "David Brooks" wrote:
    Can you interpret a 'Crash Report'?

    If so, I'd appreciate your advice on the one shown here:-

    https://discussions.apple.com/thread/255648133

    EtreCheckPro crashed because of:

    EXC_BAD_ACCESS (SIGBUS)
    "A bus error terminated the process, often because the process tried
    to access a misaligned or invalid address in memory..."

    KERN_MEMORY_ERROR.
    "The crashed thread tried to access memory that couldn't return data
    at that moment, such as a memory-mapped file that became unavailable".

    The rest of that report means little to me and there's no traceback
    info of modules to show where it happened. If it happens consistently
    at the same point in that app, then I'd suspect a bug in it. If it
    happens randomly and with other apps, the bug could be in a library
    module or even be faulty memory.

    Thank you so very much for responding, Ant.

    The possibility of faulty memory - is your suggestion that memory on my computer may be at fault?

    If so, can you suggest a way in which I can test that?

    =

    (I've shared this response with the UK Mac Usenet group)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Brooks@21:1/5 to David Brooks on Mon Jun 17 11:13:42 2024
    XPost: alt.computer.workshop

    On 16/06/2024 13:27, David Brooks wrote:
    On 16/06/2024 12:13, Apd wrote:
    "David Brooks" wrote:
    Can you interpret a 'Crash Report'?

    If so, I'd appreciate your advice on the one shown here:-

    https://discussions.apple.com/thread/255648133

    EtreCheckPro crashed because of:

    EXC_BAD_ACCESS (SIGBUS)
    "A bus error terminated the process, often because the process tried
    to access a misaligned or invalid address in memory..."

    KERN_MEMORY_ERROR.
    "The crashed thread tried to access memory that couldn't return data
    at that moment, such as a memory-mapped file that became unavailable".

    The rest of that report means little to me and there's no traceback
    info of modules to show where it happened. If it happens consistently
    at the same point in that app, then I'd suspect a bug in it. If it
    happens randomly and with other apps, the bug could be in a library
    module or even be faulty memory.

    Thank you so very much for responding, Ant.

    The possibility of faulty memory - is your suggestion that memory on my computer may be at fault?

    If so, can you suggest a way in which I can test that?

    =

    (I've shared this response with the UK Mac Usenet group)

    FYI - https://discussions.apple.com/thread/255650024?sortBy=oldest_first

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)