ea4278754c
* chore: fix spelling in .circleci Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in BUILD.gn Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in appveyor.yml Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in build Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in docs Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in lib Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in script Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in shell Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in spec Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in spec-main Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
71 lines
2.4 KiB
Markdown
71 lines
2.4 KiB
Markdown
# Electron Debugging
|
|
|
|
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.
|
|
|
|
## Generic Debugging
|
|
|
|
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, amongst other things.
|
|
|
|
Some examples:
|
|
|
|
```cpp
|
|
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: `INFO`, `WARN`, and `ERROR`.
|
|
|
|
See [logging.h](https://chromium.googlesource.com/chromium/src/base/+/refs/heads/main/logging.h) in Chromium's source tree for more information and examples.
|
|
|
|
## Printing Stacktraces
|
|
|
|
Chromium contains a helper to print stack traces to console without interrupting the program.
|
|
|
|
```cpp
|
|
#include "base/debug/stack_trace.h"
|
|
...
|
|
base::debug::StackTrace().Print();
|
|
```
|
|
|
|
This will allow you to observe call chains and identify potential issue areas.
|
|
|
|
## Breakpoint Debugging
|
|
|
|
> Note that this will increase the size of the build significantly, taking up around 50G of disk space
|
|
|
|
Write the following file to `electron/.git/info/exclude/debug.gn`
|
|
|
|
```gn
|
|
import("//electron/build/args/testing.gn")
|
|
is_debug = true
|
|
symbol_level = 2
|
|
forbid_non_component_debug_builds = false
|
|
```
|
|
|
|
Then execute:
|
|
|
|
```sh
|
|
$ 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.
|
|
|
|
## Platform-Specific Debugging
|
|
<!-- TODO(@codebytere): add debugging file for Linux-->
|
|
|
|
- [macOS Debugging](debugging-on-macos.md)
|
|
- [Debugging with Xcode](debugging-with-xcode.md)
|
|
- [Windows Debugging](debugging-on-windows.md)
|
|
|
|
## 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](debugging-with-symbol-server.md).
|