A sticky mode would be helpful. Can you use JIT debugging with DebugBreak()? Should suspend the process at the DebugBreak(), preventing it from handling the deactivation messages and shutting down. This might enable you to step through the code once. That's assuming Chrome.exe doesn't trap the interrupt. Remote debugging is another alternative (two machines or an emulator like VirtualPC or VMWare).
-----Original Message----- From: Michael Weber [mailto:[email protected]] Sent: Monday, November 16, 2009 12:54 PM To: Chromium-extensions Subject: [chromium-extensions] is there a "sticky mode" available for debugging browser actions that use NPAPI plugins? My extension uses an NPAPI plugin and I need to debug my C++ code in the context of a browser action. Of course, clicking anywhere outside the browser action causes it to close, along with the chrome instance that is hosting my DLL. At least, I assume a transient instance of chrome hosts my dll. I see additional chrome instances spawn when I open my browser action. But, it is impossible to check which DLLs are loaded using any tool, since the moment you go to use another tool, you implicitly dismiss the browser action. Unless I am missing some obvious way to attach a debugger to my NPAPI code, I desperately need a way to make the browser action stay open, even when it loses input focus, so I can debug my darned code. thx! Michael -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=. -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=.
