Hi, Sam, The IPC applies for the single process model. They use the same high level objects, like MessageLoop, Channel.
If you want to know this more, suggest practice to add a new message like, ViewMsg_SetActive: From: Sam Nazi [mailto:[email protected]] Sent: Monday, May 11, 2015 10:23 AM To: Xu, Xing; [email protected] Subject: Re: [Crosswalk-help] [crosswalk-help] What is latest tool/command line option for debugging xwalk renderer process Hello Xing, Do you mean reply to the crosswalk-help list instead? I guess I forgot to hit reply all previously. I have already read most of the documents from the links you point to. Since xwalkwalk android is single process model, does IPC (inter-process-communication) mechanism still applied to the single process model here? Or does it use different communication mechanism between threads (between browser thread and renderer thread) , such as message queue, or something else? Thank you! On Fri, May 8, 2015 at 10:52 PM, Xu, Xing <[email protected]<mailto:[email protected]>> wrote: Hi, Sam, please refer to: https://www.chromium.org/developers/design-documents/inter-process-communication There are a lot of useful document here: https://www.chromium.org/developers/design-documents BTW, please ask question on the mailing list. From: Sam Nazi [mailto:[email protected]<mailto:[email protected]>] Sent: Saturday, May 9, 2015 1:27 AM To: Xu, Xing Subject: Re: [Crosswalk-help] [crosswalk-help] What is latest tool/command line option for debugging xwalk renderer process Hi Xing, Thank you for your information. I was able to use the adb_gdb xwalk for debugging into xwalk core shell process. in this case , what communication mechanism is engaged between browser and render threads? Through message queue (base/message_loop)? Is it handled by the same chromium IPC layer or totally separated ? I try to understand this that definitely helps me a lot down the road. The question might be beyond xwalk scope, and thank you again for you helps! On Thu, May 7, 2015 at 5:45 PM, Xu, Xing <[email protected]<mailto:[email protected]>> wrote: Crosswalk for android is single process. There is no separate render process. You can debug it with: (For arm:) . ./xwalk/build/android/envsetup.sh adb_gdb_xwalk_core_shell --debug --target-arch=arm --start (For x86) . ./xwalk/build/android/envsetup.sh adb_gdb_xwalk_core_shell --debug --target-arch=ia32 --start From: Crosswalk-help [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Sam Nazi Sent: Friday, May 8, 2015 8:38 AM To: [email protected]<mailto:[email protected]> Subject: [Crosswalk-help] [crosswalk-help] What is latest tool/command line option for debugging xwalk renderer process Hello, Saw this comments from crosswalk android debugging web page. Just wonder what is the latest tool/command line I should use for debugging into renderer process on native level. * [Deprecated] To debug the renderer process, use: adb_gdb_xwalk_core_shell --verbose --sandboxed=[0-6] The above is from the website: https://github.com/crosswalk-project/crosswalk-website/wiki/Android-debugging Thanks a bunch!
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
