Fix: BMDA version command output #1951
Open
+69
−65
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
…r and not the BMDA console when the user requests the version information, and tidied up how it's generated
…arameters to the commands
…s in switch-case blocks
…atting the probe information out to GDB for the version command
dragonmux
added
Bug
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.
Detailed description
In this PR we address where the output of
monitor versionin GDB was being put under BMDA and what exactly was being reported.This brings BMDA closer to being consistent with the other platforms, reducing user surprise, and making the output of
mon vermore helpful when users are facing issues by providing which BMDA version and probe they're using precicely.We have taken the opportunity to update the copyright string in the process.
Your checklist for this pull request
Closing issues