EdgeDbg has been deprecated on Windows Creators Edition and up.https://github.com/SkyLined/EdgeDbg/blob/master/README.md …
-
-
Replying to @berendjanwever
EdgeWinDbg works if you manually resume some of the suspended processes in taskmgr/procexp in case anyone wants a workaround
1 reply 0 retweets 0 likes -
Replying to @sizzop
That's not how it works: you won't be debugging all the processes and will miss crashes.
1 reply 0 retweets 0 likes -
Replying to @berendjanwever
Okay. I tried verifying with a crashing test case but didn't look into it very far. This wouldn't work, right?https://github.com/MicrosoftEdge/edge-launcher …
1 reply 0 retweets 0 likes -
Replying to @sizzop
Not sure what you are asking; launching Edge != debugging Edge.
1 reply 0 retweets 0 likes -
Replying to @berendjanwever
Sorry, I mean loading edgelauncher in windbg with .childdbg
1 reply 0 retweets 0 likes
That would allow you to debug edge launcher but not Edge. You may want to read up on how UWP Apps work; it's rather complex to debug them :(
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.