Using DebugInfo #1259
Merged
Using DebugInfo #1259
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
Member
|
hey @StevenCostiou, I imaging this is ok, but can you take a look? This is your domain after all :P |
Member
|
I know its there I need to have a look :p |
Contributor
|
So I can merge and we check because this is important that this PR does not rot. |
guillep
added a commit
to guillep/NewTools
that referenced
this pull request
Nov 24, 2025
Updating the UI does a full refresh, expecting to update only when the entire state of the debugger is new. Thus, calling updateStep loses the scroll, and sometimes forces a scrolling to the beginning.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This PR makes use of the new debug info interface.
This API, which is to be used in tools such as debugger, inspector, is responsible of reading variables from a context, and to obtain bytecode to source code mappings:
...
Particular care is taken for optimized/inlined contexts, and avoiding creeping implementation details to users!!
Depends on: pharo-project/pharo#18644