DAP: introduce Rdbg Trace Inspector #959
Merged
Conversation
This file contains 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
ono-max
changed the title
ono-max
force-pushed
the
rdbg-inspector
branch
2 times, most recently
from
02b0216 to
4dc44d3
Compare
ono-max
changed the title
ko1
reviewed
Apr 21, 2023
lib/debug/frame_info.rb
Outdated
| @@ -147,6 +147,17 @@ def local_variables | |||
| end | |||
| end | |||
|
|
|||
| def get_params | |||
There was a problem hiding this comment.
def iseq_parameters_info
...
when :block, :method
parameters_info
else
nil
end
ko1
reviewed
Apr 21, 2023
| module DAP_TraceInspector | ||
| class MultiTracer < Tracer | ||
| MAX_LOG_SIZE = 4000 | ||
| def initialize ui, evts, trace_params, **kw |
ono-max
force-pushed
the
rdbg-inspector
branch
8 times, most recently
from
35eef6a to
c38c836
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.
Summary
We introduce Rdbg Trace Inspector. This is useful when tracing in VS Code. Users can search tracing logs easily and get a lot of useful information by using Rdbg Trace Inspector. For example, users can know which method is called, which line is executed, local variables at some point, and so on.
How to use it
That's it! You can check the location and returned value by clicking the trace log.
Several demos
Trace Call/Return
Users can know which method is called, its parameters, and return values.
Screen.Recording.2023-04-16.at.14.50.48.mov
Record & Replay
This is slow, but Users can get a wealth of information by enabling Record & Replay. For example, users can know the backtrace and local variables during the execution.
Screen.Recording.2023-04-16.at.14.28.48.mov
Other
Trace Call and Trace Line are enabled in the default. Users can select Record & Replay from the menu.
Also, users can enter Regular Expressions to trace only matched events as follows.
Screen.Recording.2023-04-17.at.15.36.52.mov
Users can copy the specific log as follows:
Screen.Recording.2023-04-22.at.16.23.42.mov
Some Notes: This PR is the combination of #946 and #916. After discussing with @ko1-san, we decided to combine record inspector and trace inspector.