Changes between Version 22 and Version 23 of WebKitGTK/Debugging
- Timestamp:
- Mar 25, 2020, 6:02:32 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WebKitGTK/Debugging
v22 v23 11 11 }}} 12 12 13 On 32-bit architectures it's quite unlikely this build will succeed. If you need a build with debug symbols but still without ASSERTs enabled you can try these options :13 On 32-bit architectures it's quite unlikely this build will succeed. If you need a build with debug symbols but still without ASSERTs enabled you can try these options. '''Note''', these options are no longer available. This needs an update: 14 14 {{{ 15 15 #!sh … … 17 17 }}} 18 18 19 If you want to debug the web process, the simplest way is to connect to it using gdb:19 If you are not using the Flatpak SDK and you want to debug the web process, the simplest way is to connect to it using gdb: 20 20 {{{ 21 21 $ gdb -p <pid of WebKitWebProcess> … … 23 23 However that doesn't work in all cases, because the web process might already have crashed when you are trying to connect to it. 24 24 25 You can use the '''WEB_PROCESS_CMD_PREFIX''' environment variable (only works on Debug builds) for that purpose. If that variable is defined the web process will be run using its value as a prefix. 25 If you are using the Flatpak SDK and you want to debug the web process, the simplest way is to connect to it using gdb: 26 {{{ 27 $ Tools/Scripts/webkit-flatpak --command=gdb /app/webkit/WebKitBuild/Debug/bin/WebKitWebProcess 28 }}} 29 30 31 You can use the '''WEB_PROCESS_CMD_PREFIX''' environment variable (only works on Developer builds, `build-webkit` or regular CMake enabled with `-DDEVELOPER_MODE=ON`) for that purpose. If that variable is defined the web process will be run using its value as a prefix. 26 32 27 33 Example: 28 34 {{{ 29 WEB_PROCESS_CMD_PREFIX='/usr/bin/gdbserver localhost:8080' WebKitBuild/Debug/bin/MiniBrowser35 WEB_PROCESS_CMD_PREFIX='/usr/bin/gdbserver localhost:8080' Tools/Scripts/run-minibrowser --gtk --debug 30 36 }}} 31 37 and in a different terminal: 32 38 {{{ 33 $ cd WebKitBuild/Debug 34 $ gdb -q bin/WebKitWebProcess 39 $ Tools/Scripts/webkit-flatpak --command=gdb /app/webkit/WebKitBuild/Debug/bin/WebKitWebProcess 35 40 Reading symbols from bin/WebKitWebProcess...done. 36 41 (gdb) target remote localhost:8080 … … 40 45 If you want to debug the network process you can use '''NETWORK_PROCESS_CMD_PREFIX''' in a similar way. 41 46 42 Note that these variables are only enabled in debug builds. If you still want to use them in release builds you can remove the relevant43 '''#ifndef NDEBUG''' in '''ProcessLauncherGtk.cpp''',44 '''ProcessLauncher.h''', '''WebProcessProxyGtk.cpp''' and45 '''NetworkProcessProxySoup.cpp'''46 47 47 An alternative to using a command prefix is to set the '''WEBKIT2_PAUSE_WEB_PROCESS_ON_LAUNCH''' environment variable. This will pause the web process for 30 seconds, giving you time to attach in a debugger before it starts. 48 48 … … 50 50 51 51 This works both with release and debug builds. If you are trying to get a backtrace from the WebKitGTK+ packages shipped by your distribution, '''ensure you have the corresponding dbgsym packages installed'''. 52 53 == Without Systemd 52 54 53 55 * Open a terminal/shell, and enable coredumps … … 78 80 79 81 82 == With Systemd and coredumpctl enabled 80 83 84 {{{ 85 $ Tools/Scripts/webkit-flatpak --gdb -m WebKitWebProcess 86 (gdb) t a a bt 87 }}} 81 88 89 This should also work: 82 90 91 {{{ 92 $ Tools/Scripts/webkit-flatpak --gdb-stack-trace -m WebKitWebProcess 93 }}} 83 94 84 95 == Logging support == 85 96 86 Logging and other output/behaviors support is activated by default in a ''Debug'' build only.97 Logging and other output/behaviors support is activated when the `-DUSE_SYSTEMD=ON` CMake option is used. 87 98 88 99 In addition to having the logging support activated in the compilation, we need also to turn on the proper logging channels when running.
