Require explicit bounded frame disassembly tools #42
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/vfsd!42
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/require-explicit-bounded-frame-disassembly-tools"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Require an explicitly selected disassembler, the maintained Integration process-owner closure and a new evidence directory for each frame observation. Missing or linked helpers and cached foreign modules cannot substitute the selected owner; imports restore the caller’s module cache and finder.
The standalone CI step sources its prepared Cargo gateway and checks the ELF from its actual target directory. The original 30-second native-command bounds and 240 KiB runtime/smoke frame ceiling remain unchanged.
Refs #1. Depends on #41.
WIP: Require explicit bounded frame disassembly toolsto Require explicit bounded frame disassembly toolsPrepared a single-commit history at
c50660d5e4b42bfec832ab50f947a3bffdf0547bonfeature/require-explicit-bounded-frame-disassembly-tools-merge-ready-c50660d5. It folds the feature correction and drops two changes already present upstream. The complete tree is identical to the current source head; both histories remain available. Please review this prepared commit for merging into the existing linker-script work branch.