Open Bug 1635139 Opened 5 years ago Updated 1 year ago

Local Talos profiling symbolication on Windows requires "mach buildsymbols"

Categories

(Testing :: Talos, defect, P3)

Product:
Testing
Component:
Talos
Version:
Version 3
Platform:
All
Windows
Type:
defect

Tracking

(Not tracked)

People

(Reporter: mstange, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [fxp])

When you run mach talos-test --geckoProfile [...] locally, on Windows, the resulting profiler recordings do not have symbols for xul.dll, unless you run mach buildsymbols first.

On macOS and Linux, they have symbols even without mach buildsymbols, because symbolication.py will use dump_syms_mac or nm to get symbols.

We could land a Windows version of dump_syms in there as well, and use that. There are probably other cleaner solutions.
(For example, these days we have taskcluster jobs which produce dump_syms artifacts, so there's probably a way to download the artifact from the latest such job, rather than putting a binary into the source tree.)

Priority: -- → P3
Severity: -- → S3

Bug 1720356 would fix this.

Depends on: 1720356
Whiteboard: [fxp]
You need to log in before you can comment on or make changes to this bug.