Segmentation fault when using latest biicode release

[Manu343726]

Hi Tobias.

I have discovered a biicode/boost-examples-headeronly build job that failed surprisingly. Travis has usually problems handling my huge >60jobs builds and job VMs fail once in a while, usually with network connection issues.

In this case, an internet connection error make bii unable to download my cmakepp track, so bii downloaded master track instead, your latest block release.
Having Boost failing when using your block causes no problem for me, since I don't ever tested Boost with latest versions of cmakepp. I'm coming here since the build fails with CMake raising a segmentation fault, something that IMHO deserves in depth analysis. I don't wanna see users having segfaults when using cmakepp ;) we are lucky we caught this "internally". Note that I'm not sure is a cmakepp problem, my scripts, or a combination of both.

Here's the build job.

[toeb]

Hi Manu,

the problem with this as well as the ls issue is that I cannot see what happens. Most of the time when I encountered segfaults with cmake/cmakepp it was because of infinite recursion.

I'll try to come to fixing it but currently I'm a little preoccupied - can't make any promises :(