Add --il-offset option to source command for IL offset resolution

[slang25]

Summary

Adds an --il-offset option to the source command that resolves method token + IL offset pairs to source file locations using PDB sequence points.

This is useful when working with stacktraces from .NET runtimes that include IL offsets instead of line numbers (e.g., Tizen, or environments where symbols aren't available at runtime). With Switch.System.Diagnostics.StackTrace.ShowILOffsets enabled, stacktraces include entries like:

at MyApp.Program.Main() in MyApp.dll: token 0x6000001+0x5

This option translates that token+offset into the actual source file and line number.

Usage

# Basic usage with a local library
dotnet inspect source --library MyApp.dll --il-offset 0x6000001+0x5

# With a platform library
dotnet inspect source --platform System.Text.Json --il-offset 0x6000004+0x15

# JSON output
dotnet inspect source MyPackage --il-offset 0x6000002+0x1 --json

# Markdown view with full details
dotnet inspect source --library MyApp.dll --il-offset 0x6000001+0x5 -v

Implementation

• SourceLinkResolver: New ResolveByILOffset() method walks PDB sequence points to find the best matching source line. Works with and without SourceLink (falls back to file path + line when no SourceLink URLs are available).
• SourceCommand: Early branch in ExecuteAsync skips API extraction (not needed — the token identifies the method directly). Parses and validates the token+offset hex format, rejecting non-MethodDef tokens.
• Output: Supports oneline (default), markdown (-v), and JSON (--json) output formats via a dedicated SourceILOffsetView and ILOffsetResult.
• Tests: Parser validation tests for valid and invalid token+offset formats.

Closes #322

[richlander]

Thanks. Will take a look.

[richlander]

Thanks for this — the feature works correctly end to end. I verified IL-offset resolution against PDB sequence points across exact, in-between, and boundary offsets, and the malformed/out-of-range token paths all fail gracefully.

I pushed a small follow-up branch, review/il-offset-improvements (commit 5f852b6), with two optional tidy-ups. Please take them, adapt them, or ignore them — entirely your call.

1. Dedup the resolver. ResolveByILOffset and ResolveByILOffsetDirect were ~50 near-identical lines. I collapsed the shared sequence-point walk into the single static ResolveByILOffsetDirect; the instance method now just enriches the result with SourceLink URLs via record ... with. Same behaviour, net −53 lines. Also switched sp.StartLine != SequencePoint.HiddenLine to !sp.IsHidden to match the convention used elsewhere in the file.

2. Tests for the walk. The parser was already covered, but the sequence-point resolution itself wasn't. Added ILOffsetResolutionTests (against a real PDB) covering exact sequence-point offsets, an in-between offset resolving to the preceding point, and the non-MethodDef / out-of-range null paths.

I left the System.Text.Json full-qualification as-is — it matches the existing style in SourceCommand.cs.

If it's easier than eyeballing the branch, you can pull the commit directly:

git fetch https://github.com/richlander/dotnet-inspect.git review/il-offset-improvements
git cherry-pick 5f852b6

[slang25]

@richlander those changes make sense, I've pulled them in 🙂

[richlander]

I'll finish this up tomorrow. The rendering doesn't quite work the same as other commands. I already made some changes. I'll push those in the morning.

[richlander]

SourceILOffsetView emitted a single fixed inline field block at every verbosity level — -v:q, -v:n, and -v:d all produced identical output. Every other view in the tool gates content by verbosity and renders structured data as ## sections rather than loose inline fields.

The change: reshape the view to follow the library (LibraryInspectionView) discipline:

Level	Output
-v:q	compact inline line: Token … | IL Offset … | Matched Offset …
-v:m (default)	## Offset section only
-v:n / -v:d	## Offset + ## Source (file / line / URL)

Source content is reserved for normal+, matching how source <type> reveals detail progressively. --json and --oneline are unchanged. Patch version bumped to 0.7.11.

Pushed to il-offset-sections (commit c0b874f) to pull from.

[richlander]

Thanks! Published.