Reading from the bottom up, we start with a bunch of external event machinery, which led to the invocation of an event handler, evidently the OnSettingsChanged handler. This is a big, ugly stack, but we can simplify it: Contoso!winrt:: impl:: consume_ IWidgetWatcher:: Notif圜hange+0x3Ĭontoso!winrt:: WidgetController:: SaveWidget+0x16Ĭontoso!winrt:: impl:: consume_ IWidgetController:: SaveWidget+0xdĬontoso!winrt:: Widget:: OnSettingsChanged$_ ResumeCoro$1+0x31fĬontoso!winrt::Widget:: OnSettingsChanged$_ ResumeCoro$1+0x11aĬontoso!winrt::Widget:: OnSettingsChanged$_ InitCoro$2+0圆aĬontoso!winrt::Widget:: OnSettingsChanged+0x5cĬontoso!winrt:: TypedEventHandler:: :: operator()+0x5bĬontoso!winrt:: impl:: delegate:: Invoke+0圆d Rpcrt4!LRPC_ SASSOCIATION:: HandleRequest+0x2c3 Rpcrt4!LRPC_ SCALL:: QueueOrDispatchCall+0x253 Rpcrt4!LRPC_ SBINDING:: DispatchToStubWithObject+0x23 Rpcrt4!RPC_ INTERFACE:: DispatchToStubWithObject+0x188 Rpcrt4!RPC_ INTERFACE:: DispatchToStub+0xb3 Rpcrt4!RPC_ INTERFACE:: DispatchToStubWorker+0x1b4 The stack of the crash looked like this: Contoso!winrt:: impl:: consume_ Contoso_ IWidgetWatcher:: Notif圜hange+0x3Ĭontoso!winrt:: Contoso:: implementation:: WidgetController:: SaveWidget+0x16Ĭontoso!winrt:: impl:: produce:: SaveWidget+0x1dĬontoso!winrt:: impl:: consume_ Contoso_ IWidgetController:: SaveWidget+0xdĬontoso!winrt:: Contoso:: implementation:: Widget:: OnSettingsChanged$_ ResumeCoro$1+0x31fĬontoso!std:: experimental:: coroutine_ handle:: resume+0xcĬontoso!winrt:: impl:: await_ adapter:: await_ suspend+0x15eĬontoso!winrt:: Contoso:: implementation:: Widget:: OnSettingsChanged$_ ResumeCoro$1+0x11aĬontoso!winrt:: Contoso:: implementation:: Widget:: OnSettingsChanged$_ InitCoro$2+0圆aĬontoso!winrt:: Contoso:: implementation:: Widget:: OnSettingsChanged+0x5cĬontoso!winrt:: Windows:: Foundation:: TypedEventHandler:: :: operator()+0x5bĬontoso!winrt:: impl:: delegate, >:: Invoke+0圆dĬombase!InvokeStubWithExceptionPolicyAndTracing:: _ _ l6:: :: operator()+0x22Ĭombase!ObjectMethodExceptionHandlingAction >+0x4dĬombase!InvokeStubWithExceptionPolicyAndTracing+0xe1 A customer had a mysterious crash in a C++/WinRT coroutine, and they were having trouble identifying the cause.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |