3da363517f
2.0 KiB
Using gdb against Element-Desktop
Occasionally it is useful to be able to connect to a running Element-Desktop
with gdb, or to analayze a coredump. For this,
you will need debug symbols.
-
If you don't already have the right version of Element-Desktop (eg because you are analyzing someone else's coredump), download and unpack the tarball from https://packages.element.io/desktop/install/linux/. If it was a nightly, your best bet may be to download the deb from https://packages.element.io/debian/pool/main/e/element-nightly/ and unpack it.
-
Figure out which version of Electron your Element-Desktop is based on. The best way to do this is to figure out the version of Element-Desktop, then look at
package.jsonfor the corresponding version. There will be an entry withindependenciesofelectron: the value will tell you the version of Electron that was used for that version of Element-Desktop. -
Go to Electron's releases page and find the version you just identified. Under "Assets", download
electron-v<version>-linux-x64-debug.zip(or, the -debug zip corresponding to your architecture). -
The debug zip has a structure like:
. ├── debug │ ├── chrome_crashpad_handler.debug │ ├── electron.debug │ ├── libEGL.so.debug │ ├── libffmpeg.so.debug │ ├── libGLESv2.so.debug │ └── libvk_swiftshader.so.debug ├── LICENSE ├── LICENSES.chromium.html └── versionTake all the contents of
debug, and copy them into the Element-Desktop directory, so thatelectron.debugis alongside theelement-desktop-nightlyexecutable. -
You now have a thing you can gdb as normal, either as
gdb --args element-desktop-nightly, orgdb element-desktop-nightly core.