Repository navigation
Conversation
The runtime's own statements of where its code and build ID sit, so consumers read these facts from gobin instead of re-deriving Go layout knowledge. - Add GoBinary::text_bound_words: the addresses of the words that hold the text bounds (moduledata minpc/maxpc/text/etext, each textsectmap base, pcHeader.textStart on Go 1.18-1.25, the Go 1.2-1.17 functab end sentinel), so a tool collecting code pointers can drop them by site. - Add GoBinary::build_id_blob, the file extent of the raw build ID marker (Mach-O, PE, wasm); None for an ELF note. - Add GoBinary::text_section_end_va, the end of the textsectmap section holding the last byte of Go code. - Add TextSect::va_range and the bounds::TEXT_SYMBOL / ETEXT_SYMBOL names. - Breaking: ModuledataLocator::locate returns LocatedModuledata, and buildid::extract returns a BuildId with its BuildIdSource. - Fix the TextSect field docs: vaddr and end are offsets from runtime.text, not addresses.
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.
Release 0.6.0: the runtime's own statements of where its code and build ID sit, so consumers read these facts from gobin instead of re-deriving Go layout knowledge.
Added
GoBinary::text_bound_words: the addresses of the words holding the text bounds (moduledataminpc/maxpc/text/etext, eachtextsectmapbase,pcHeader.textStarton Go 1.18-1.25, the Go 1.2-1.17 functab end sentinel).GoBinary::build_id_blob: the file extent of the raw build ID marker (Mach-O, PE, wasm);Nonefor an ELF note.GoBinary::text_section_end_va: the end of thetextsectmapsection holding the last byte of Go code.TextSect::va_range,bounds::TEXT_SYMBOL,bounds::ETEXT_SYMBOL.Breaking
ModuledataLocator::locatereturnsLocatedModuledata.buildid::extractreturns aBuildId(ID plusBuildIdSource) instead of&str.GoBinary::build_idis unchanged.Fixed
TextSectfield docs:vaddrandendare offsets fromruntime.text.Verification
Locally, on a checkout outside the path-patch config:
cargo fmt --check,cargo clippy -- -D warnings(and--all-targets),cargo docwith-D warnings,cargo teston stable and 1.88 (168 unit, 118 integration, 4 doc), andcargo publish --dry-run. New accessors are checked across the sample corpus against independent oracles (marker bytes, ELF section headers, ELF symbol tables).Cargo.lockchanges only the gobin version line.