test: stabilize shared CFI backtrace e2e#234
Merged
Merged
Conversation
0147181 to
a538f7a
Compare
Run the shared-CFI target-mode backtrace case against the spawned target PID while keeping the standalone -t cross-module case unchanged. This isolates CFI sharing from target-discovery offset refresh timing. Start target-mode backtrace targets paused, wait briefly after GhostScope is ready, then resume them so assertions exercise steady-state unwinding. Keep container docs explicit that nested child-container target-mode coverage is partial while globals_target cases still skip.
a538f7a to
17e0512
Compare
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.
Sample the shared-CFI backtrace script so the test exercises both probes without saturating script output.
Update container docs to match the nested child-container target-mode coverage that now runs in CI.