[SOLVED] JLink.exe crashes when used with Sophos Endpoint Security

  • Hi All,

    I've been having issues with JLink.exe crashing when Sophos Endpoint Security (anti-virus software) is active.

    I have a crash dump file, but it's too large to attach (3.4MB). Is there anyone I can send this to?
    I did attach a .zip file with the Metadata and version info.
    It appears there's an access violation or unhandled exception in swi_ifslsp.dll from Sophos.
    Our company is using about 20 of the J-Link probes for engineering and production use.

    It turns out there's an interesting workaround: if you run one instance of JLink.exe and let it sit in the background, other instances won't crash.

    I loaded the memory dump file into Visual Studio 2012, but the debugger doesn't have access to the JLink.exe internals.

    Thanks for any thoughts you might have or who I can share the crash dump file with.

    Thanks,
    Tim
    nLIGHT Photonics
    Vancouver, WA
    JLinkSophosCrash2.zip

  • Hi All,

    Just a quick update. I was able to do some more experimentation with Sophos anti-virus. When I set "Block access to malicious websites" to Off and reboot the computer, JLink.exe runs fine without any problems.

    Related Sophos knowledgebase articles: 118563, 111225, 116970

    Cheers,
    Tim

  • Hi,

    Quote

    I have a crash dump file, but it's too large to attach (3.4MB). Is there anyone I can send this to?


    Feel free to send it as attachment to https://www.segger.com/support/technical-support/
    We will also try to reproduce this error.

    Best regards,
    Niklas

    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: https://www.segger.com/ticket/

    Or you can contact us via e-mail.

  • I tried JLink 5.10h that was released today and it fixes the issue!

    Many thanks to the Segger development team for fixing this in a timely manner. This can be marked as [SOLVED]

    Cheers,
    Tim
    nLIGHT Corporation

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!