Closed Bug 1340809 Opened 8 years ago Closed 8 years ago

Consider automatically generating build symbols for local builds if --enable-profiling is on

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox54 affected)

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox54 --- affected

People

(Reporter: mstange, Unassigned)

Details

At the moment, when you profile a local build, the Gecko profiler addon has to dump symbols from your local binaries. On Mac this is done using an ASM.js version of the breakpad dump_syms tool, on Linux it's done by starting an "nm" process, and on Windows it's currently completely unimplemented. If our build system always created plain text symbol information automatically, the addon could just consult those generated files. Is this feasible? How much would it slow down build times?
Flags: needinfo?
Flags: needinfo?
I just ran mach buildsymbols on my machine and it printed > Worker finished processing dist/bin/XUL in 160.25s This is clearly too long to do it every time libxul changes.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.