I just made a new issue ticket:
https://github.com/therion/therion/issues/278
Am 2020-10-14 22:53, schrieb Benedikt Hallinger:
Hi there,
i performed a git bisect (the very first in my lifetime, and that is
really a nice and easy tool to search such things!!!).
The commits at and before c7d41d9 compiled the cave sucessfully 10 of
10 times.
1c1fcf14e4eaf6e0bb89da513702ad9b89204ed8 is the first bad commit
commit 1c1fcf14e4eaf6e0bb89da513702ad9b89204ed8
Author: mbudaj <m.bu...@gmail.com>
Date: Wed Aug 19 07:25:53 2020 +0200
dynamically load EPSG/ESRI labels in Proj>=6
https://github.com/therion/therion/commit/1c1fcf14e4eaf6e0bb89da513702ad9b89204ed8
This compiles unstable like described before.
Am 2020-10-14 22:32, schrieb Wookey:
On 2020-10-14 22:05 +0200, Benedikt Hallinger wrote:
OK, now i got something.
Guess what - one of about 5 compiles runs trough.
This leads me to think that there is a race condition or something
else
somewhere, overwriting memory of the to-be-checked string.
I'm pretty sure now that this is not a problem with the dataset per
se, but
some memory issue of the compiled therion program.
The following pattern resulted in several runs with 5.5.2 (n=failed,
y=ok):
nnnynnynnynynynynnny
Oh dear. This could be fun to track down....
Better check 5.5.1 always works, not just more often. But if it does
then careful examination of what changed is in order. Maybe send some
others the dataset to see who can reproduce (windows/linux/macOS)?
Wookey
_______________________________________________
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion
_______________________________________________
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion
_______________________________________________
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion
