Why I can't see the stack of my app in the crash dump?

See more:

Windows

Metro-design

crash

I am not sure if I'm having the wrong expectation in regards to analyze a crash dump in Visual Studio 2013.

I'm trying to learn about crashdump analysis; so I want to see if I can make an app crash and analyze the crashdump. So, I create a Metro app with one button. I press the button (handled by myButton_Click) which instantiate a class (MyClass) and calls a method (doWork). In my method I do an operation that causes crash (in this case just trying to do an operation in a null).

I used procdump.exe to configure the system to generate the dump (procdump.exe -ma -i c:\crashdumps).

I generated the metro package and deployed in my dev machine. Open the app, clicked the button and the app crashed as expected and I can see the dump in c:\crashdumps.

I extracted the MyApp.appx and MyApp.appxsym in a folder called c:\debug

I open the crashdump file in Visual Studio 2013 and click on Set Symbol paths and include a new path (c:\debug)

Then I click on Debug with Mixed.

Under the Locals panel I see a description of the error that I forced indeed. But I don't see any stack. I was expecting to see my myButton_Click, MyClass.constructor and the MyClass.doWork. Am I having the wrong expectation? Or am I doing something wrong. I read several sites already but I am not sure what's going on.

BTW. If I see output panel; I see that the EXE inside of the APPX is listed with a bunch of other modules. All the modules show "Symbol loaded" in the end. But in my EXE doesn't show in the end. So I wonder if the symbol was even loaded. But I think I did right. No?

Thank you in advance