On Fri, Aug 16, 2024 at 10:46:22AM +0200, Jan Eden via isync-devel wrote:
Although I found a practical solution (i.e. a working order), I would be grateful if someone could explain what is going on here.
a bug, rather obviously. is the problem reproducible with `mbsync -ls`? if not, with `mbsync -a -l`? does specifying the stores/channels on the command line in different orders yield different results, or does it depend only on the config file? run the simplest failing invocation through valgrind/memcheck. make sure to build with -Og -g3, as otherwise the traces won't be too useful. if valgrind finds no problems, run with -Dn, one working and one failing invocation, so we can compare the logs. it may also make sense to repeat that with strace. mail me the logs in private. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
