Open
Bug 1803284
Opened 2 years ago
Updated 2 years ago
Some sources are mislinked in symbol files
Categories
(Toolkit :: Crash Reporting, defect)
Toolkit
Crash Reporting
Tracking
()
NEW
People
(Reporter: glandium, Unassigned)
Details
While working on bug 1798660, I detected a bunch of things that are going wrong that I figured I'd file a bug about. They may or may not be worth fixing.
- A sort of regression from bug 1798660: the symbol files now link to s3 for Unified_*.* files that aren't in the generated sources archive (before, they would stay as paths on the worker).
- On Windows builds, paths for rust source files of the rust standard library have a path like
/builds/worker/workspace/obj-build/toolkit/library/build/C:/Users/runneradmin/.cargo/registry/src/...
which probably doesn't match what crash reports and/or profiler are associating with rust sources. - On Windows builds, paths for C sources files of the MSVC runtime have a path like
/builds/worker/workspace/obj-build/toolkit/library/build/d:/agent/_work/2/s/src/...
. - Some source files, notably in gfx/angle and gfx/harfbuzz, but also in other places, are sources generated from something else but that we have in the tree as source, and they contain
#line
directives that make the debug info contain the file name listed there (relative to the current directory at the time the file is compiled), rather than the "real" source file we have, which leads to the source paths in the symbol files that don't match any file that exists. Examples of such files areglslang.l
,preprocessor.l
,hb-buffer-deserialize-json.rl
, etc.
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:gsvelto, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(gsvelto)
Updated•2 years ago
|
Severity: -- → S3
Flags: needinfo?(gsvelto)
You need to log in
before you can comment on or make changes to this bug.
Description
•