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
Implement --debugger option to improve UX when debugging crashes #13157
Conversation
I didn't test but I did read through the code and the code looks good. And it seems like a nice feature. |
dcde792
to
b30226d
Compare
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.
Works on Linux. I haven't tested thoroughly on Windows (I'm using Wine).
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.
Tested on Windows too now.
Instead of trying to direct users to enter the magic words to start gdb and then pull out a backtrace with this PR we can just tell them to add a single argument.
This is so seamless that you could even add it to your startup script and have e.g. the server always run under gdb.
To do
This PR is a Work in Progress
How to test
./bin/minetest --debugger
optionally add a segfault bug somewhere first to see what happens