There are many different approaches to debugging issues and bugs in Electron, many of which are platform specific.
Some of the more common approaches are outlined below.
Chromium contains logging macros which can aid debugging by printing information to console in C++ and Objective-C++.
You might use this to print out variable values, function names, and line numbers, amonst other things.
LOG(INFO) << "bitmap.width(): " << bitmap.width();
LOG(INFO, bitmap.width() > 10) << "bitmap.width() is greater than 10!";
There are also different levels of logging severity:
See logging.h in Chromium's source tree for more information and examples.
Chromium contains a helper to print stack traces to console without interrrupting the program.
This will allow you to observe call chains and identify potential issue areas.
Note that this will increase the size of the build significantly, taking up around 50G of disk space
Write the following file to
is_debug = true
symbol_level = 2
forbid_non_component_debug_builds = false
$ gn gen out/Debug --args="import(\"//electron/.git/info/exclude/debug.gn\") $GN_EXTRA_ARGS"
$ ninja -C out/Debug electron
Now you can use
LLDB for breakpoint debugging.
Debugging with the Symbol Server
Debug symbols allow you to have better debugging sessions. They have information about the functions contained in executables and dynamic libraries and provide you with information to get clean call stacks. A Symbol Server allows the debugger to load the correct symbols, binaries and sources automatically without forcing users to download large debugging files.
For more information about how to set up a symbol server for Electron, see debugging with a symbol server.