+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Development (https://forum.cuberite.org/forum-13.html)
+--- Thread: Catching Travis core dumps (/thread-2140.html)
Pages:
1
2
RE: Catching Travis core dumps - worktycho - 11-01-2015
I am now apposed to this. I think we lose more by leaving the container based infrastructure, than we gain in having the occasional core dump.
RE: Catching Travis core dumps - Seadragon91 - 11-01-2015
The best is then to wait until there is a fix or some way to get the core in containers. I closed the pull request.
RE: Catching Travis core dumps - Seadragon91 - 03-18-2017
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
RE: Catching Travis core dumps - xoft - 03-19-2017
That looks great, by all means push it in