none
No call stack information available in WEC2013 .kdmp file? RRS feed

  • Question

  • Hi all,

    We have a .kdmp file (on a WEC 2013) system which reports a crash in NDIS. We suspect our ethernet driver to call an NDIS function with invalid arguments. In order to find out from which source line, we want to have a call stack at the time of the crash. Unfortunately, when loading the .kdmp file into Platform Builder, we do not see the call stack.
    It turns out that the memory area of the stack is not available in the kdmp file. We expect the stack to be available as this would be part of the Thread Environment Block (TEB).
    We experimented with the DumpType in the HKLM\System\ErrorReporting\DumpSettings but this does not seem to get more data about the offending thread.

    Does anyone have a suggestion on how to proceed?

    Thanks in advance,

    Marcel
    Thursday, February 23, 2017 8:44 AM

All replies

  • Hi Marcel,

    This is a known bug that we (and some other MVPs) have reported a long time ago to Microsoft. The MS CE support team is currently gathering information and trying to reproduce the issue (it all seems to work on CEPC they say). Hopefully we will have a fix soon.

    I assume you are on an ARM platform (i.MX6 IIRC), so that would help the team at MS. What would also help is if you open another support incident with MS so they know it's not just a single occurrence but that this bug affects many customers.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, February 23, 2017 8:51 AM
    Moderator
  • Hi Marcel and Michel,

    WEC2013 KDMP files also don't work for me. Is Michel stated, there is no call stack information which makes the KDMP useless. Michel, were you able to find a workaround to this problem?

    When trying to expand the call stack for each thread in a process we see the following:

    Thanks,

    Jared


    Friday, April 28, 2017 9:31 PM
  • Microsoft has been unable to reproduce this issue in house, and if they can't reproduce they can't fix the issue.

    It is very important you open a support incident with Microsoft explaining exactly what version of the OS, which BSP and to what level you have updated your tools and build tree.

    Did you open a support incident already? If not; please do asap. If yes; please let us know the result here.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Friday, April 28, 2017 10:13 PM
    Moderator
  • I just got an update from the MS support team about this bug. They have now been able to reproduce and the product team is looking into this issue as we speak.

    It would still be good for you to open a support incident so they can prioritize this issue. The more people reporting the same bug, the higher the impact and thus the higher the priority.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Saturday, April 29, 2017 8:13 AM
    Moderator
  • Hi Michel,

    I've opened a support incident with Microsoft and am now corresponding with the support engineer.

    Thanks for being so responsive!

    Jared

    Tuesday, May 2, 2017 3:39 AM
  • Update: I verified they fixed this issue on our platform and Microsoft is planning on releasing the fix in the WEC2013 May monthly update, which is targeted for June 13th. Yeah!
    Thursday, May 18, 2017 3:14 PM
  • Great news! Thanks for reporting back here!

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, May 18, 2017 4:16 PM
    Moderator