Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only print evaluate requests in REPL context #1334

Merged
merged 1 commit into from
Aug 10, 2022

Conversation

WardenGnaw
Copy link
Member

@WardenGnaw WardenGnaw commented Aug 10, 2022

This PR fixes the EvaluateRequest with an -exec command and assign the return protocol with the correct Value.

This causes the DebugConsole in VS Code to show the output as a REPL output instead of an engine output.

Old:
ret-exec-val-old

New:
ret-exec-val

Fixes: #1236

@WardenGnaw WardenGnaw added the VS Code VS Code label Aug 10, 2022
@WardenGnaw WardenGnaw self-assigned this Aug 10, 2022
@WardenGnaw WardenGnaw force-pushed the dev/waan/evaluateOutputREPL branch from bbbdb86 to b49b232 Compare August 10, 2022 20:26
This PR checks to see if the `-exec` commands are originally from the
REPL context (e.g. the Debug Console). If so, it will redirect the
output of the -exec command to the REPL window. If it is another
context, it will not print anything.
Copy link
Collaborator

@andrewcrawley andrewcrawley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit message should be updated, but otherwise LGTM!

@WardenGnaw WardenGnaw merged commit 93c8040 into main Aug 10, 2022
@WardenGnaw WardenGnaw deleted the dev/waan/evaluateOutputREPL branch August 10, 2022 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
VS Code VS Code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The result of GDB -exec evaluate request in all contexts is printed in debug console.
2 participants