symbolication returns "line: 0" for symbols in SYM files with no line information
Categories
(Eliot :: General, defect, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
References
Details
Attachments
(1 file)
If we have a SYM file that has symbols and no LINE information, then doing lookups with symbolic will return "line: 0" as part of the LineInfo.
For example, minidump-stackwalk will return something like this:
{
"frame": 0,
"function": "KiFastSystemCallRet",
"function_offset": "0x0",
"module": "ntdll.dll",
"module_offset": "0x470b4",
"offset": "0x771b70b4",
"trust": "context"
},
And the new symbolication API that uses symbolic will return something like this:
{
"frame": 0,
"function": "KiFastSystemCallRet",
"function_offset": "0x0",
"line": 0,
"module": "ntdll.dll",
"module_offset": "0x470b4",
"offset": "0x771b70b4",
"trust": "context"
},
As near as I can tell, this only occurs with SYM files from system libraries and other situations where we don't have the source code. If we don't have the source code, there isn't anything to look at for line 0, so maybe this isn't wildly important. I'm making it a P3 for now.
However, it is weird that "line: 0" indicates it's an invalid value for the line.
Comment 1•3 years ago
|
||
As for the profiler, this doesn't cause any trouble because these results don't have a "file" property. The profiler only looks at the "line" property of results that also have a "file" property.
Assignee | ||
Comment 2•3 years ago
|
||
That's incredibly helpful to know!
I'll fix the code to check for the file and if there's no file, then drop the line from the outgoing data because it doesn't make any sense.
Assignee | ||
Comment 3•3 years ago
|
||
Assignee | ||
Comment 4•3 years ago
|
||
Assignee | ||
Comment 5•3 years ago
|
||
I merged this to main and deployed it to stage. We should be good here.
Assignee | ||
Updated•1 year ago
|
Description
•