The 2.6 client gets the version message, parses it fine until it gets to the subver string then throws errors. As a result it cannot read the block height that comes after. The substr issue is the issue we are looking into, could be due to sending serialised string as the numbers before worked.
We have found the exact line of code where 0.13 stops syncing, basically PoS hash does not meet the target. The block is Decemeber 2017. Not sure if it is a bit of a rogue block or of the issue is with the new client.Peter Will get all values for CheckStakeKernelHash from 2.6 and compare tomorrow.
I can see where Peter has pushed a few commits to the xbcwalletsource repo to deal with compiler warnings during the compilation process.
https://github.com/bitcoinplusorg/xbcwalletsource/commit/d933f8c010fd6034166ac16df3f66c6020461a5a
https://github.com/bitcoinplusorg/xbcwalletsource/commit/49d312bda6f0186308c6e34f26b3830966d50ba7
https://github.com/bitcoinplusorg/xbcwalletsource/commit/d893c88ecbeb9579a9dc016514e2705f4ffaf45b
https://github.com/bitcoinplusorg/xbcwalletsource/commit/f5e66f794ba81834a9aec249316650ffed6098ec