On Fri, Apr 03, 2015 at 12:38:24PM +0200, Dmitrij D. Czarkoff wrote: > I use mbsync to sync Gmail account to local mailbox. After an update > 1.0.6 -> 1.1.2 I started seeing messages: > > | Warning: lost track of 1 pulled message(s) > > followed by dumping core without error messages. > the first thing you should do when you get a core dump is loading it into gdb and creating a backtrace. provided the build has debug symbols ...
> This only happens in sent mail folder, which is odd, because that > folder is never modified locally. > "pull" means "download" in a typical mbsync configuration, so nothing odd here. > The warning repeats on sequential runs. > yeah, the log shows a history of failures. > Is there any more data I can provide? > the backtrace (and even more, a valgrind log) would be the most valuable option. you can add -V to see the communication with the server, which might give a bit of context to the crash. there have been previous reports of crashes related to the use of Group, so you could see what happens if you specify only the affected Channel on the command line. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
