dbgr: allow dumping the backtrace to a file #2284
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
xTVaser
force-pushed
the
v/backtrace-to-file
branch
from
d12c1d5
to
4cbbac7
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.
Some backtraces are quite large, an option is to increase your terminal buffer -- but dumping to a file is also useful if you want to share the crash.
I'm not crazy about the way I hacked this in, but it felt like the least invasive way for now and I don't want to cause a regression with the debugger. It's also nice that it dumps with ansi colors as then you can view the backtrace with the original coloring:
Usage: