Open arajkumar opened 9 years ago
This should be fairly easy to fix if you want to submit a patch. It just lists only chrome.exe's, so it would be really easy to include content_shell. On the other hand, Attach to Chrome is kind of deprecated in favor of Microsoft's official child process debugging tool https://visualstudiogallery.msdn.microsoft.com/a1141bff-463f-465f-9b6d-d29b7b503d7a. In part because I don't really work on Chrome anymore, and don't have time to make improvements to Attach to Chrome, but also in part because it just does everything Attach to Chrome does but better and more flexible, being that it's officially supported by the same people who made the debugger to begin with.
On Tue, Jun 9, 2015 at 9:41 PM Arunprasad Rajkumar notifications@github.com wrote:
DEBUG->Attach to Chrome doesn't shows content_shell processes.
— Reply to this email directly or view it on GitHub https://github.com/chromium/vs-chromium/issues/19.
DEBUG->Attach to Chrome
doesn't shows content_shell processes.