Catching Travis core dumps
#11
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.
Reply
Thanks given by:
#12
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.
Reply
Thanks given by:
#13
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  Big Grin

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  Smile


Funny side note, now no core dump required  Tongue
Reply
Thanks given by:
#14
That looks great, by all means push it in Smile
Reply
Thanks given by:




Users browsing this thread: 1 Guest(s)