03-18-2017, 06:56 AM
(This post was last modified: 03-18-2017, 01:56 PM by Seadragon91.)
Found this nice stackoverflow answer.
gdb starts Cuberite and if Cuberite exits, gdb will run the commands bt, "info threads" and "thread apply all bt". At last it exits with the exit code of Cuberite.
Tested this idea in a commit and it works fine
Travis (crash): All runs, clang debug
Travis(no crash): All runs, clang debug
If you like this idea, then I will create a pull request
Funny side note, now no core dump required
gdb starts Cuberite and if Cuberite exits, gdb will run the commands bt, "info threads" and "thread apply all bt". At last it exits with the exit code of Cuberite.
Tested this idea in a commit and it works fine
Travis (crash): All runs, clang debug
Travis(no crash): All runs, clang debug
If you like this idea, then I will create a pull request
Funny side note, now no core dump required