Closed
Bug 1411897
Opened 7 years ago
Closed 7 years ago
no attribute 'get_debugger_info' when trying to launch named debugger via mach run
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(firefox58 affected)
RESOLVED
DUPLICATE
of bug 1411776
Tracking | Status | |
---|---|---|
firefox58 | --- | affected |
People
(Reporter: hsivonen, Unassigned)
Details
On Ubuntu 17.10: $ ./mach run --disable-e10s --debug --debugger=rr Error running mach: ['run', '--disable-e10s', '--debug', '--debugger=rr'] The error occurred in the implementation of the invoked mach command. This should never occur and is likely a bug in the implementation of that command. Consider filing a bug for this issue. If filing a bug, please include the full output of mach, including this error message. The details of the failure are as follows: AttributeError: 'module' object has no attribute 'get_debugger_info' File "/opt/Projects/gecko/python/mozbuild/mozbuild/mach_commands.py", line 1420, in run self.debuggerInfo = mozdebug.get_debugger_info(debugger, debugger_args) $ ./mach run --disable-e10s --debug Error running mach: ['run', '--disable-e10s', '--debug'] The error occurred in the implementation of the invoked mach command. This should never occur and is likely a bug in the implementation of that command. Consider filing a bug for this issue. If filing a bug, please include the full output of mach, including this error message. The details of the failure are as follows: AttributeError: 'module' object has no attribute 'get_default_debugger_name' File "/opt/Projects/gecko/python/mozbuild/mozbuild/mach_commands.py", line 1417, in run debugger = mozdebug.get_default_debugger_name(mozdebug.DebuggerSearch.KeepLooking)
Updated•7 years ago
|
Component: mach → Build Config
Comment 1•7 years ago
|
||
Smells like a dupe of bug 1411776. Reopen if you can repro on head of mozilla-central.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•