Confirmed users
753
edits
Mobile/Fennec/Android/GDB: Difference between revisions
→Running JimDB
No edit summary |
|||
| Line 179: | Line 179: | ||
This will automatically start gdbserver and fennec on the device, and start gdb on your computer. | This will automatically start gdbserver and fennec on the device, and start gdb on your computer. | ||
=== First run of JimDB === | |||
Run JimDB, type as usual 'continue' to actually start running Fennec, give it several seconds, and hit Ctrl+C to interrupt Fennec. | |||
The first time, it will probably complain: | |||
Program received signal SIGINT, Interrupt. | |||
warning: Could not load shared library symbols for org.mozilla.fennec_bjacob. | |||
Do you need "set solib-search-path" or "set sysroot"? | |||
Do not worry about this. It will seem frozen for several seconds, but let it run. What's happening is that it's pulling all the libraries from the device into the moz-gdb directory. Ignore the suggestion about setting solib-search-path/sysroot, JimDB will do it all for you. Once it's done, you get a GDB invite as usual. | |||
Do this sanity check: | |||
(gdb) info shared | |||
For each loaded library you'll see whether symbols were found: Yes, No, or "Yes (*)" meaning no debug info. Press Enter until the listing is complete. You want to make two things sure: | |||
* Ensure that libXUL has debug info i.e. you should see a plain Yes for libxul.so. If not, that means that something is wrong with your fennec build (is it a non-debug build?) or with your gdbinit (see above). | |||
* Ensure that no library has a No. Typically, some system drivers will give you a No. For each such library, you want to manually pull it from the device into moz-gdb/lib/<device hex id>/path. These drivers are typically found in /vendor on your device. | |||