Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 7355 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Crash in swi_ifslsp_64.dll

JadeKoskela

This is on Windows 7. Here is the call stack:

> swi_ifslsp_64.dll!000007fefc2729d0() Unknown
  swi_ifslsp_64.dll!000007fefc272f4e() Unknown
  swi_ifslsp_64.dll!000007fefc27116e() Unknown
  swi_ifslsp_64.dll!000007fefc2679a0() Unknown
  [External Code]
  libcurl.dll!Curl_getaddrinfo_ex(const char *, const char *, const addrinfo *, Curl_addrinfo * *) Line 123 C
  libcurl.dll!getaddrinfo_thread(void *) Line 276 C
  [External Code]


This thread was automatically locked due to age.
  • 0
    Hi,

    What process crashed?

    The Sophos Layered Service Provider (LSP) dll you mention (swi_ifslsp_64.dll) is loaded into a process (the one in question must have been a 64-bit process) if it makes a Winsock call.

    I assume there is a Windows Event Log entry from Windows Error Reporting (WER) at the same time the process crashed and more than likely this will reference a dump file. The dump file is likely to be required; all I can tell is that a process using the Curl library made a call which resulted in a Winsock call, which in turned called into the Sophos LSP.

    If there is no dump file, I would suggest running ProcDump (technet.microsoft.com/.../dd996900.aspx) from Sysinternals and register that as the post mortem debugger. E.g. Create a directory called: C:\dumps\ then run:
    procdump -accepteula -ma -i c:\dumps

    Reproduce the problem, the process should crash and create a full dump of the process.

    I'd be happy to look at the dump if you can make it available.

    Regards,
    Jak