On Mon, Jul 2, 2012 at 3:40 PM, Dave Abrahams <d...@boostpro.com> wrote: > > on Mon Jul 02 2012, Oswald Buddenhagen <ossi-AT-kde.org> wrote: > >> it won't eat your mail (afaik), but it will hang, crash and/or make a >> mess of the sync state under various (error) conditions. i.e., i >> sincerely wouldn't recommend using it. >> i recently looked into the code again. if nothing sidetracks me again, i >> may finally mainline it ... >> https://lists.sourceforge.net/lists/listinfo/isync-devel > > So, what if I just apply the s/%%/\*/ patch, that searches for all IMAP > subfolders, to the latest release? Is there a reliability problem > waiting there to bite me? Note: I don't care about Maildir.
To answer my own question, mbsync(90223) malloc: *** error for object 0x7fabb280b800: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug So I guess the next question is, what does "make mess of the sync state" mean, and how bad is it? If there are issues with the async branch that I can help you track down, I'd be willing to try. -- Dave Abrahams BoostPro Computing http://www.boostpro.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
