fix(debugging): support probes on declarations - #19873
Draft
tylfin wants to merge 2 commits into
Draft
Conversation
Circular import analysis
|
Dependency direction analysis
|
Codeowners resolved asResolved from the full PR diff against |
tylfin
commented
Aug 26, 2026
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.
Description
Allow Dynamic Instrumentation line probes placed on function or method declarations to install successfully. Function discovery records code-object header ranges and redirects these probes to the first executable line without parsing application source. The configured source line remains unchanged in emitted probe metadata and the effective line is retained for probe removal.
Testing
scripts/lint checksRisks
Code-object line metadata can differ between Python versions. The fallback is limited to locations that resolve to exactly one function header, while ordinary executable-line probes retain their existing behavior.