New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support PLMDebug (windows store app debugging) #1698

mrexodia opened this Issue Aug 28, 2017 · 0 comments


None yet
1 participant

mrexodia commented Aug 28, 2017

  1. Install WinDbg (and open a command prompt next to windbg.exe)
  2. Locate MicrosoftEdge.exe (C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\ for me)
  3. Open AppxManifest.xml it should contain the version (38.14393.1066.0 for me):
<Identity Name="Microsoft.MicrosoftEdge" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" Version="38.14393.1066.0" ProcessorArchitecture="neutral"/>
  1. Run the command plmdebug.exe /enableDebug Microsoft.MicrosoftEdge_38.14393.1066.0_neutral__8wekyb3d8bbwe C:\CodeBlocks\x64dbg\bin\x96dbg.exe it should output:
Package full name is Microsoft.MicrosoftEdge_38.14393.1066.0_neutral__8wekyb3d8bbwe.
Enable debug mode
  1. Start Edge, it will start x64dbg.exe with the following command line:
C:\CodeBlocks\x64dbg\bin\x96dbg.exe -p 12400 -tid 10708

This command line is undocumented. WinDbg accepts -p as the process id (decimal), but -tid is undocumented/unsupported. It corresponds to the thread id (decimal) of the main thread, but this might be different if Edge is already running... thread to resume after attach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment