Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[AUTOMATED]
Scope
Add a standalone bounded MSF 7 stream reader for future PDB work. It exposes the PDB information stream's GUID, age, signature and version, without connecting the reader to the evaluator or changing any score, cache or existing backend. The limits and unsupported formats are documented.
This is a small building block for the native Windows work discussed in #36; API naming and future integration should be coordinated with maintainers. It does not require #91. Reading an identity does not establish that a PDB belongs to a PE: a future integration must compare the PE's CodeView GUID and age. It does not parse PDB types, symbols or function ranges.
Validation