On 04/29/17 19:35, Ketil Malde wrote:
>
> > I'm still waiting for my big run to complete, but I have a smaller test
>
> Unfortunately, the new executable appears to fail for the same data that
> the old one did. So if there is indeed a subtle bug hidden in libjudy,
> it doesn't seem to be affect
> I just built a version with using the -fno-strict-aliasing and
> -fno-aggressive-loop-optimizations compiler options:
Great, thanks for the quick response! I did a dpkg -i *.deb of your
files, rebuilt my executable (statically linked, but I think that would
pick up the new version?), and start
> Would you please download and test that version and see if you are
> able to still duplicate the segfault?
I'm still waiting for my big run to complete, but I have a smaller test
case which has been particularly troublesome (and which leads to corrupt
output). Unfortunately, using the new Judy
> I'm still waiting for my big run to complete, but I have a smaller test
Unfortunately, the new executable appears to fail for the same data that
the old one did. So if there is indeed a subtle bug hidden in libjudy,
it doesn't seem to be affected by these options.
I also tried this on multipl
