Still segfaults:
sonicle@wwwclone:/sonicle/var/spool/imap/domain/sonicle.com/user/test^big$ squatter -v -i -s -a -r user/test.big@xxxxxxxxxxx
Indexing mailbox user/test.big@xxxxxxxxxxx... Doing incremental for mailbox sonicle.com!user.test^big... Segmentation Fault (core dumped)
sonicle@wwwclone:/sonicle/var/spool/imap/domain/sonicle.com/user/test^big$ mdb core
Loading modules: [ libc.so.1 ld.so.1 ]
> $C
ffffdf7fffdfd910 add_to_table+0x2f1()
ffffdf7fffdfd950 add_word_to_trie+0x51()
ffffdf7fffdfd9d0 dump_index_trie_words+0x190()
ffffdf7fffdfde30 index_close_internal+0x2ca()
ffffdf7fffdfde50 squat_index_finish+0x1d()
ffffdf7fffdfdff0 squat_single+0x414()
ffffdf7fffdfe8f0 index_me+0x489()
ffffdf7fffdff940 main+0x32b()
ffffdf7fffdff950 _start+0x6c()
sonicle@wwwclone:/sonicle/var/spool/imap/domain/sonicle.com/user/test^big$ squatter -v -i -s -a -r user/test.big@xxxxxxxxxxx
Indexing mailbox user/test.big@xxxxxxxxxxx... Doing incremental for mailbox sonicle.com!user.test^big... Segmentation Fault (core dumped)
sonicle@wwwclone:/sonicle/var/spool/imap/domain/sonicle.com/user/test^big$ mdb core
Loading modules: [ libc.so.1 ld.so.1 ]
> $C
ffffdf7fffdfd910 add_to_table+0x2f1()
ffffdf7fffdfd950 add_word_to_trie+0x51()
ffffdf7fffdfd9d0 dump_index_trie_words+0x190()
ffffdf7fffdfde30 index_close_internal+0x2ca()
ffffdf7fffdfde50 squat_index_finish+0x1d()
ffffdf7fffdfdff0 squat_single+0x414()
ffffdf7fffdfe8f0 index_me+0x489()
ffffdf7fffdff940 main+0x32b()
ffffdf7fffdff950 _start+0x6c()
I now run it with valgrind again, it will take time.
Sonicle S.r.l. : http://www.sonicle.com
eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets
Da: Robert Stepanek <rsto@xxxxxxxxxxxxxxxx>
A: Gabriele Bulfon <gbulfon@xxxxxxxxxxx>Gabriele Bulfon via Info <info@xxxxxxxxxxxxxxxxxx>
Data: 11 maggio 2021 13.54.40 CEST
Oggetto: Re: Squatter core dump
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
