On Mon, Jul 02, 2012 at 08:11:40PM -0400, Dave Abrahams wrote: > 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 > yeah, something like that. ^^
did you patch the 1.0 branch or master? try the other one, maybe you get more lucky with that. > So I guess the next question is, what does "make mess of the sync > state" mean, and how bad is it? > i can't really answer that. it's pre-alpha code, not tested much, and even that has been a year ago. i still have at least one semi-major refactoring to do, because i discovered a design problem which makes exception handling of any kind inherently unreliable (c.f., the above error message). ------------------------------------------------------------------------------ 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
