NativeSymbolStatus
Namespace: Dotsider.Core.Analysis.Models
Assembly: Dotsider.Core.dll
The outcome of probing a binary for native symbols. When no symbols are returned, the status distinguishes the reasons — missing, mismatched, corrupt, ambiguous, or fallback-only — so callers can explain the result instead of showing an empty table with no cause.
public enum NativeSymbolStatusFields
Section titled “Fields”AmbiguousImage
Section titled “AmbiguousImage”A fat/universal binary offered no slice that could be disambiguated.
Returns: NativeSymbolStatus
AmbiguousImage = 5CorruptSymbolFile
Section titled “CorruptSymbolFile”A symbol file was found and matched, but could not be parsed.
Returns: NativeSymbolStatus
CorruptSymbolFile = 3FallbackOnly
Section titled “FallbackOnly”Only nameless function boundaries were recovered from unwind data.
Returns: NativeSymbolStatus
FallbackOnly = 4IdMismatch
Section titled “IdMismatch”A symbol file was found but its identity did not match the binary.
Returns: NativeSymbolStatus
IdMismatch = 2Loaded
Section titled “Loaded”Named symbols loaded from a primary source.
Returns: NativeSymbolStatus
Loaded = 0NoSymbolFile
Section titled “NoSymbolFile”No symbol file was found beside the binary and no fallback applied.
Returns: NativeSymbolStatus
NoSymbolFile = 1NotApplicable
Section titled “NotApplicable”The binary is managed or otherwise has no native symbols to read.
Returns: NativeSymbolStatus
NotApplicable = 6