3 Mar
2016
3 Mar
'16
8:24 a.m.
On Thu, Mar 3, 2016 at 11:00 PM, Peter Bortas @ Pike developers forum 10353@lyskom.lysator.liu.se wrote:
Try compileing Pike with -fsanitize=address, there's a fairly good chance that would catch exactly when things start going wrong of we are talking about any kind of over/under-flow.
While I was poking with this, Grubba pushed a fix that appears to cure the problem (both for my little test case and for the original): bdcd55, using safe_apply_value. Thanks Grubba!
Came across a really obscure compilation bug, though. Fun stuff.
ChrisA