-
Notifications
You must be signed in to change notification settings - Fork 2.2k
debugger: symlist usability + symbol table extensibility #13694
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes no sense at all. Why wouldn’t you default to the CPU that’s currently focused in the debugger rather than the first CPU? That’s what all the other commands do (
bpset
,wpset
, etc.). Always defaulting to the first CPU a very poor choice.Also, as I’ve said elsewhere, the purpose a symbol table is being used for is not a characteristic of the symbol table, and shouldn’t be a property of the symbol table. Requiring a model object to know all the situations in which it will be used is broken design.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cuavas: Sorry about that CPU thing, and thanks for catching it. I opened a PR to fix (#13886).
Regarding the symbol table type enum, I mentioned a follow-up suggestion on #13733, but hadn't heard back yet. The gist was to allow the symlist command to provide helpful category headers in its output as future symbol tables get added to the parent chain, such as local and global variables from the source code for source-level debugging. The goal is to categorize what the symbol table contains, but not exactly where or how it's used.
This allows symlist to be more data-driven, which leads to simple code even when there are 4 symbol tables chained together...
Alternatively, if symbol tables cannot know anything about their contents, then rather than looping through the symbol table parent chain, symlist would need to be hard-coded to obtain each symbol table from a known accessor / owner object so it could reliably print the descriptive header before it. This would require ongoing maintenance to the symlist code if new symbol tables are added to the parent chain in the future. I was hoping to avoid this, but if you think it's cleaner this way, I can do it.
What do you think?