jeudi 24 novembre 2016

Debugging a sigtrap in c++

In a recent program I've made I had some worrying random crashes/ crash on shutdown, after stripping down I think I've narrowed it down to a SIGTRAP which happens when a vector is created under specific circumstances. The main bulk of the code can be found here :http://ift.tt/2g8bG11 and the tile class here : http://ift.tt/2fvjyet (the issue arises when the buildworld subroutine is ran) and the console output can be found here http://ift.tt/2g8bEpV . The debugger goes to new_allicator when this happens, if that's worth knowing.

Also note that for some reason removing the calls to rTest in the tiles (which only makes a call to the RNG that class has), but only if another subZone has been created since then. Needless to say I am completely baffled as to why this is happening.

Am I doing anything dumb here? I'm only using std libraries, so I don't think I could of installed them wrong or anything. Is this an issue I can/should ignore? Any kind of help on how to approach this issue is greatly appreciated.




Aucun commentaire:

Enregistrer un commentaire