Mobile/Fennec/Android/AdvancedTopics: Difference between revisions

Remove old content that is JimDB
(Updated the commands to launch Fennec via adb)
(Remove old content that is JimDB)
 
Line 14: Line 14:


for the target specified above.  Note: you cannot use <tt>ac_add_options --disable-optimize</tt> when building for x86.  See {{bug|965870}}.
for the target specified above.  Note: you cannot use <tt>ac_add_options --disable-optimize</tt> when building for x86.  See {{bug|965870}}.
==== Building for the ARMv6 architecture ====
'''ARMv6 is no longer a supported target as of Firefox 33.'''
If you want to build for ARMv6 instead of ARMv7 (only required for very old, very low end phones), add:
ac_add_options --with-arch=armv6


==== Building different channels ====
==== Building different channels ====
Line 166: Line 158:
  adb shell setprop log.redirect-stdio true
  adb shell setprop log.redirect-stdio true
  adb shell start
  adb shell start
=== Using JimDB ===
See [[Mobile/Fennec/Android/GDB]]


=== Using Debug Intent ===
=== Using Debug Intent ===
'''Note: this is not useful with JimDB. If you want to use JimDB, just start it.'''


In order to attach before things get running, launch with:  
In order to attach before things get running, launch with:  
Line 193: Line 179:
Note: this will only work if you have symbols for dalvik.
Note: this will only work if you have symbols for dalvik.


=== Debugging with jdb ===
=== Debugging with Android Studio ===
 
JimDB can now launch JDB integration


You can also use eclipse for debugging in a similar way by setting up for debugging "Remote Java application".
See [https://mozilla.github.io/geckoview/tutorials/native-debugging.html] for Android Studio.


=== Debugging with eclipse ===
=== Debugging with eclipse ===
Confirmed users
14

edits