Changes between Version 8 and Version 9 of WebKitGTK/Debugging

Timestamp:

Dec 11, 2013 12:16:18 PM (10 years ago)

Author:

berto@igalia.com

Comment:

How to debug the web and network processes in WebKitGTK+

WebKitGTK/Debugging

@@ -86 +86 @@
 }}}
 
+== Debugging WebKit2 ==
+
+If you want to debug the web process, the simplest way is connecting to
+it using gdb:
+{{{
+$ gdb -p <pid of WebKitWebProcess>
+}}}
+However that doesn't work in all cases, because the web process might
+already have crashed when you are trying to connect to it.
+
+You can use the '''WEB_PROCESS_CMD_PREFIX''' environment variable for
+that purpose. If that variable is defined the web process will be run
+using its value as a prefix.
+
+Example:
+{{{
+WEB_PROCESS_CMD_PREFIX='/usr/bin/gdbserver localhost:8080' WebKitBuild/Debug/Programs/MiniBrowser
+}}}
+and in a different terminal:
+{{{
+$ libtool --mode=execute gdb WebKitBuild/Debug/Programs/WebKitWebProcess
+(gdb) target remote localhost:8080
+}}}
+If you want to debug the network process you can use
+'''NETWORK_PROCESS_CMD_PREFIX''' in a similar way.
+
+Note that these variables are only enabled in debug builds. If you
+still want to use them in release builds you can remove the relevant
+'''#ifndef NDEBUG''' in '''ProcessLauncherGtk.cpp''',
+'''ProcessLauncher.h''', '''WebProcessProxyGtk.cpp''' and
+'''NetworkProcessProxySoup.cpp'''
+
 == Debugging issues ==