In case anyone else needs this: How to make MicrosoftEdge (including all MicrosoftEdgeCP.exe instances) start with windbg on Win10 v1703:
-
-
Yeah, I used something similar to EdgeDbg before, but the benefit of this is you can start debugging as soon as the process gets created.
-
I can't find a way to do this in only one debugger instance: I keep getting a new WinDbg for each process, which is sub-optimal. Any tips?
-
Don't know how to do that either. Multiple instances didn't bother me and I guess browser_broker etc would require a different solution :-/
-
I could send the "-p # and -tid #" args thru a named pipe to BugId, so it can tell its cdb instance to attach... have no idea for WinDbg tho
-
This makes things even easier: windbg -plmPackage "Microsoft.MicrosoftEdge_40....yb3d8bbwe" -plmApp MicrosoftEdgehttps://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-a-uwp-app-using-windbg …
-
It says you specify an argument that is passed to the App, but that doesn't work for me :(.
-
What WinDbg and OS versions are you using? Edge is pretty unique and there could be a bug there.
-
Pretty sure it's WinDbg: WinDbg.exe -plmPackage "..." -plmApp MicrpsoftEdge foo Result is "Could not create process 'foo'" see belowpic.twitter.com/rEGqF7V2dP
- 2 more replies
New conversation -
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.