I'm seeing a handful of ParseSymFileErrors in the Mozilla Symbolication Service starting August 11th for firefox 38FBF249F41F7A64B3A6098BCC225F920.
The file record on symbols.mozilla.org is here:
https://symbols.mozilla.org/uploads/files/file/48861769
The header looks like this:
MODULE Linux x86_64 65B29E6A53804B5D86B2D3497464C71C0 firefox
INFO CODE_ID 6A9EB26580535D4B86B2D3497464C71C4EEACF30
INFO GENERATOR mozilla/dump_syms 2.2.0
65B29E6A53804B5D86B2D3497464C71C0 does not match the debug id 38FBF249F41F7A64B3A6098BCC225F920.
Did dump_syms somehow put a different debug id in the file? Is this a problem elsewhere with the build?
https://bugzilla.mozilla.org/show_bug.cgi?id=1848642
I'm seeing a handful of ParseSymFileErrors in the Mozilla Symbolication Service starting August 11th for
firefox38FBF249F41F7A64B3A6098BCC225F920.The file record on symbols.mozilla.org is here:
https://symbols.mozilla.org/uploads/files/file/48861769
The header looks like this:
65B29E6A53804B5D86B2D3497464C71C0does not match the debug id38FBF249F41F7A64B3A6098BCC225F920.Did
dump_symssomehow put a different debug id in the file? Is this a problem elsewhere with the build?https://bugzilla.mozilla.org/show_bug.cgi?id=1848642