Hi all, I help maintain JimDB, the fork of GDB used by the Fennec team, and I'd like some feedback on extending JimDB to support debugging B2G.
As a GDB fork, JimDB includes additional bug fixes and improvements over the GDB included in the Android toolchain (which is the GDB included in B2G). It also incorporates a set of Python scripts that automates most of the setup. For example, you can start debugging a Mochitest in one step, by simply specifying which test and optionally what environment variables to use. Here are some more information on JimDB's capabilities, https://wiki.mozilla.org/Android/GDB and http://www.jnchen.com/blog/2013/03/updated-jimdb I think a lot of JimDB's features are applicable to B2G as well, and through Python scripts, it can potentially do more than what the current shell script setup is capable of. For example, the script can look for apps running on your device, ask which app to debug, and automate the rest. However I'm not a B2G developer, so I'd like some feedback on whether it's worthwhile to work on this project. Do you use GDB in your workflow? Is the current GDB setup good enough? What would you like to be easier when debugging? Thanks for any comments! :) Cheers, Jim _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
