devtools: Fix available breakpoint positions with nested scripts #38826
Conversation
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
atbrakhi
approved these changes
Aug 21, 2025
Co-authored-by: atbrakhi <atbrakhi@igalia.com> Signed-off-by: Delan Azabani <dazabani@igalia.com>
361c214 to
e2ea32e
Compare
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.
in the SpiderMonkey Debugger API, there is a separate Debugger.Script object for each function in a script, forming a tree of Script objects. since we were only issuing getPossibleBreakpoints() queries to the root Script object for each script, we were failing to report locations inside functions as available for setting breakpoints.
this patch fixes that by recursively issuing the getPossibleBreakpoints() requests over the getChildScripts() tree.
Testing: this patch adds a new devtools test