Yes, but unfortunately I didn't find time to do more than that. The log pretty much confirms that there's memory corruption, with invalid reads and writes all over the place.
This line looks like a potential start to debug:
==17293== Address 0xff28149a0 is 0 bytes inside a block of size 2,056 free'd
==17293== at 0xFFFF64A29: free (vg_replace_malloc.c:549)
==17293== by 0x407A28: write_trie_word_data (squat_build.c:1364)
(interestingly, in my code the free happens at line 1363).
As a very crude attempt, you could just comment out this free() call. It will leak memory, but if that omits the segfault then we have narrowed down what's causing the corruption.
On Tue, May 11, 2021, at 1:38 PM, Gabriele Bulfon wrote:
Hight, did you have any chance to check the valgrind log I've sent?Sonicle S.r.l. : http://www.sonicle.comeXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanetsDa: Robert Stepanek <rsto@xxxxxxxxxxxxxxxx>
A: Gabriele Bulfon via Info <info@xxxxxxxxxxxxxxxxxx>
Data: 7 maggio 2021 17.45.19 CEST
Oggetto: Re: Squatter core dumpOn Fri, May 7, 2021, at 5:31 PM, Gabriele Bulfon via Info wrote:Never did, it's our illumos distro, but I may have valgrind.Can you help on this?Just running "valgrind --leak-check=full <path-to-squatter> <your-args>" should do the trick.Cheers,Robert
