mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-25 22:01:30 +00:00
6bcfb690b5
People often seek to learn how mach commands work. A common way to do this is to launch a debugger and step through the code as it is executing. But this requires someone to first find and modify the mach command. This involves overhead. This patch adds a global --debug-command argument to mach. When present, we launch an interactive debugger right before command dispatch. This allows people to easily enter a debugger to see what mach commands are doing, hopefully lowering the barrier to understanding and contributing. --HG-- extra : rebase_source : 5ebfa7f5fd89f96dac5f7cb035ab520c63b32e55 extra : amend_source : c53c988763c328020b49aa5c6245df685b6f30bc |
||
|---|---|---|
| .. | ||
| bitstring | ||
| blessings | ||
| codegen | ||
| configobj | ||
| eme | ||
| jsmin | ||
| lldbutils | ||
| mach | ||
| mock-1.0.0 | ||
| mozboot | ||
| mozbuild | ||
| mozversioncontrol/mozversioncontrol | ||
| psutil | ||
| pyasn1 | ||
| virtualenv | ||
| which | ||
| mach_commands.py | ||
| moz.build | ||
| README | ||
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243