Closed
Bug 1367907
Opened 8 years ago
Closed 8 years ago
Profiler missing ole32.dll symbols
Categories
(Core :: Gecko Profiler, enhancement)
Tracking
()
RESOLVED
INVALID
People
(Reporter: bugzilla, Unassigned)
References
()
Details
See the URL field for a profile taken by jimm.
| Reporter | ||
Comment 1•8 years ago
|
||
ddurst says that peterbe is the person to talk to about this.
Flags: needinfo?(peterbe)
Comment 2•8 years ago
|
||
I just work on the soon-to-be infra for storing of symbols. Ted fills in the blanks.
Flags: needinfo?(peterbe) → needinfo?(ted)
Comment 3•8 years ago
|
||
If someone gives me the exact debug ID of what's missing here I can try to see why, but for all of these missing symbol bugs filed recently so far the answer has been either:
1) Microsoft hasn't published the symbols
2) My script fetched the symbols, but this profile was symbolicated before they were available
Flags: needinfo?(ted)
| Reporter | ||
Comment 4•8 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #3)
> If someone gives me the exact debug ID of what's missing here I can try to
> see why
Jim, could you please grab that info from your ole32.dll?
Flags: needinfo?(jmathies)
Comment 5•8 years ago
|
||
It's 7ADCE1572B3B4F119B90637B653300DB2 . The information is in the profile.
Flags: needinfo?(jmathies)
Comment 6•8 years ago
|
||
It's not available from Microsoft:
$ curl -LI http://msdl.microsoft.com/download/symbols/ole32.pdb/7ADCE1572B3B4F119B90637B653300DB2/ole32.pd_
HTTP/1.1 404 Not Found
Cache-Control: public
Content-Length: 1245
Content-Type: text/html
Server: Microsoft-IIS/8.5
X-MSEdge-Ref: Ref A: F7CFCFC136EB4DACAC69B261ABEBE273 Ref B: ASHEDGE0213 Ref C: Wed Jun 7 11:47:31 2017 PST
X-MSEdge-Ref-OriginShield: Ref A: DFA486AC3A6B474FA56C444478EF7A91 Ref B: BLUEDGE0419 Ref C: Wed Jun 7 11:46:59 2017 PST
Date: Wed, 07 Jun 2017 18:47:31 GMT
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 7•8 years ago
|
||
I'll send them an email.
For future reference, problems like these can be reported to them via windbgfb at microsoft.com
You need to log in
before you can comment on or make changes to this bug.
Description
•