Confirmed users
586
edits
Platform/GFX/Quantum Render: Difference between revisions
→Debugging: Be more explicit about debugging for content processes
m (→Building: Formatting tweaks) |
(→Debugging: Be more explicit about debugging for content processes) |
||
| Line 170: | Line 170: | ||
You need this because there's no way in Android Studio currently to tell the content-process instance of lldb about the search paths (the UI pane only applies to the parent-process instance of lldb). Also note that when doing native code debugging with lldb, you'll hit a "segfault" at [https://searchfox.org/mozilla-central/rev/20df68a5f5b5e078a11fa62a681f09debda61d79/mozglue/linker/ElfLoader.cpp#1283 this line] on startup; this is expected and can be ignored. {{bug|1506009}} tracks Rust code debugging, which has not yet been tested extensively. | You need this because there's no way in Android Studio currently to tell the content-process instance of lldb about the search paths (the UI pane only applies to the parent-process instance of lldb). Also note that when doing native code debugging with lldb, you'll hit a "segfault" at [https://searchfox.org/mozilla-central/rev/20df68a5f5b5e078a11fa62a681f09debda61d79/mozglue/linker/ElfLoader.cpp#1283 this line] on startup; this is expected and can be ignored. {{bug|1506009}} tracks Rust code debugging, which has not yet been tested extensively. | ||
Note that to debug a content process, you have to attach to it explicitly. After starting the app in a debug configuration from Android Studio, click on the "Attach debugger to Android process" icon (tall rectangle with a bug on it) in the toolbar and select the process you want to attach to. You can be attached to multiple processes at the same time. | |||
=== Bisecting === | === Bisecting === | ||