This commit is contained in:
David Baker
2025-05-21 13:00:45 +01:00
parent a0db96d50d
commit 20f28abb47

View File

@@ -3,11 +3,14 @@
There are two parts of the desktop app that you might want to debug. There are two parts of the desktop app that you might want to debug.
## The renderer process ## The renderer process
This is the regular element-web codeand can be debugged by just selecting 'toggle developer tools' This is the regular element-web codeand can be debugged by just selecting 'toggle developer tools'
from the menu, even on ppackaged builds. This then works the same as chrome dev tools for element web. from the menu, even on ppackaged builds. This then works the same as chrome dev tools for element web.
## The main process ## The main process
This is debugged as a node app, so: This is debugged as a node app, so:
1. Open any chrome dev tools window 1. Open any chrome dev tools window
1. Start element with the `--inspect-brk` flag 1. Start element with the `--inspect-brk` flag
1. Notice that you now have a little green icon in the top left of your chrome devtools window, click it. 1. Notice that you now have a little green icon in the top left of your chrome devtools window, click it.
@@ -15,6 +18,7 @@ This is debugged as a node app, so:
You are now debugging the code of the desktop app itself. You are now debugging the code of the desktop app itself.
## The main process of a package app ## The main process of a package app
When the app is shipped, electron's "fuses" are flipped, editing the electron binary itself to prevent certain features from being usable, one of which is debugging using `--inspect-brk` as above. You can flip the fuse back on Linux as follows: When the app is shipped, electron's "fuses" are flipped, editing the electron binary itself to prevent certain features from being usable, one of which is debugging using `--inspect-brk` as above. You can flip the fuse back on Linux as follows:
``` ```