In case anyone else needs this: How to make MicrosoftEdge (including all MicrosoftEdgeCP.exe instances) start with windbg on Win10 v1703:
-
-
Replying to @ifsecure
Interesting! Maybe this can be used to improve EdgeDbg?https://github.com/SkyLined/EdgeDbg/blob/master/README.md …
1 reply 0 retweets 10 likes -
Replying to @berendjanwever
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.
1 reply 0 retweets 4 likes -
Replying to @ifsecure
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?
2 replies 0 retweets 0 likes -
Replying to @berendjanwever @ifsecure
Note that this does not appear to debug browser_broker.exe, ApplicationFrameHost.exe or RuntimeBroker.exe processes.
1 reply 0 retweets 0 likes -
Replying to @berendjanwever @ifsecure
MicrosoftEdgeCP.EXE is launched via the DCOMLaunch service now. Of course, so are lots of other things :)
1 reply 0 retweets 3 likes
Yes, EdgeDbg does not work on Edge 40 because of this. Maybe I should just debug the service and all its children :/https://github.com/SkyLined/EdgeDbg …
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.