We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
option 1: make the current register display in ui_processed be double-columned, so we can increase vertical density
option 2: make the register display just a free-form text box we manually layout (cf selection ergonomics #4)
option 3: put them nested under frames in the stackwalk
option 4: same as option 3, but make it collapsable?
I'm inclined to 1 or 2, but 3/4 has precedent in minidump-stackwalk --human
In principle this UX question also extends to any future attempts to expose recovered function arguments.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
option 1: make the current register display in ui_processed be double-columned, so we can increase vertical density
option 2: make the register display just a free-form text box we manually layout (cf selection ergonomics #4)
option 3: put them nested under frames in the stackwalk
option 4: same as option 3, but make it collapsable?
I'm inclined to 1 or 2, but 3/4 has precedent in minidump-stackwalk --human
In principle this UX question also extends to any future attempts to expose recovered function arguments.
The text was updated successfully, but these errors were encountered: