Open Bug 1495040 Opened 6 years ago Updated 2 years ago

Make mach run --debug specify the correct flags to cope with the launcher process

Categories

(Firefox Build System :: General, enhancement)

Product:
Firefox Build System
Component:
General
Platform:
Unspecified
Windows
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: inj+)

Since it doesn't really make sense for most developers to ./mach run --debug without also attaching to the launcher's children, we should add the appropriate flags to make the debugger do the right thing.
Keywords: in-triage
See the "Debugging the browser process" section here for the motivation behind this bug: https://groups.google.com/d/msg/mozilla.dev.platform/xSyK4r54Ifs/ncc-8irMDAAJ
Keywords: in-triage
With :kmoir's consent, I'm reviewing the backlog for bugs in FFx Build System to see if we can do some things to clean up the backlog. This bug appears to be an enhancement or feature request. If so, please set the bug's severity to `enhancement` and/or add the `feature` keyword depending on if this is an improvement to an existing thing, or a new feature/tool/system.
Flags: needinfo?(aklotz)
Severity: normal → enhancement
Flags: needinfo?(aklotz)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.