Closed Bug 822254 Opened 13 years ago Closed 13 years ago

Missing symbols for probably new win32 DLLs

Categories

(Socorro :: General, task)

x86
Windows 7
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kairo, Unassigned)

References

Details

At least for some Win7 and Vista DLLs, we now seem to be missing symbols, see the top items on https://crash-analysis.mozilla.com/rkaiser/2012-12-16/2012-12-16.firefox.17.explosiveness.html for example. A few examples I pulled from a random set of crash reports: Win7: KERNELBASE.dll 6.1.7600.17135 486BB50357A24BC5A6EE88BB1FBBF7451 wkernelbase.pdb KERNELBASE.dll 6.1.7600.17135 33018FDD4369486EA70F4374FBCAD77E2 kernelbase.pdb KERNELBASE.dll 6.1.7601.17965 E1609DE3233B4EDF8211CF7E83211B401 wkernelbase.pdb KERNELBASE.dll 6.1.7601.17965 D0699EACAF4547299B4C8917FC1A490D2 kernelbase.pdb Vista: kernel32.dll 6.0.6002.18704 57533A14965F4D99AF218C4507D953E02 wkernel32.pdb kernel32.dll 6.0.6002.18704 882A637ABACB4AD29751B511B0D3A5BF2 kernel32.pdb Ted, do we have those symbols on our servers? Is something wrong with the script that should pull those from Microsoft?
There's also Win8 ones missing: KERNELBASE.dll 6.2.9200.16451 F073108B992B4AA9A1E9D51E49534A3B2 wkernelbase.pdb KERNELBASE.dll 6.2.9200.16451 DD4522B344B04180A82AA5F4E0378A1A2 kernelbase.pdb
I can confirm that these symbols are definitely not present on the symbol server. I'll poke at the Windows symbol fetcher and see if I can determine why.
I don't have any insight here, I kicked off a manual run of the symbol fetch script, it looks like it's picked up a few of these (but I'm not sure why it wouldn't have in its nightly automated runs...). I think we need to get some more visible logs out of this script so that we can diagnose things a little better.
Those were picked up, but I'm just right now filing yet another bug on another set of MS symbols missing.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Blocks: 829987
You need to log in before you can comment on or make changes to this bug.