I compiled 3.0.6pre1, including the crtimes and fileflags patches for
use on Intel OS X 10.5.6, as described by Mr. Bombich (thanks!) here:
<http://www.bombich.com/mactips/rsync.html>
I want to use 3.0.6 because it seems that this bug:
<https://bugzilla.samba.org/show_bug.cgi?id=5365>
has been resolved (yay!).
-----
[~]$ rsync --version
rsync version 3.0.6pre1 protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes, file-flags
-----
However, now I'm getting these kinds of messages throughout my output:
-----
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard sketch. 01.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard sketch 00.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 03.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 02.psd
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 02.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 01.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leanord 01.jpg
-----
and not _just_ related to deleting stuff, bercause I get this too:
-----
Mail Folder/Trash
rsync(68157) malloc: *** error for object 0x8066b8: Non-aligned
pointer being freed
*** set a breakpoint in malloc_error_break to debug
Spool Folder/
Spool Folder/In.temp
rsync(68157) malloc: *** error for object 0x334760: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
-----
and so on. This doesn't seem to be affecting my backups at all, but I
thought y'all might like to know about it. I haven't included my
rsync commands, because I don't think that's what the problem is, but
they're pretty much along the lines of -aNHAXvhtb --fileflages with a
--backup-dir and an --exclude-from and --delete and --fake-super. I
may not need the H.
Thanks.
--
W. Oates
[sorry if this appears twice -- I'm having trouble with my Gmail filters] I compiled 3.0.6pre1, including the crtimes and fileflags patches for use on Intel OS X 10.5.6, as described by Mr. Bombich (thanks!) here: <http://www.bombich.com/mactips/rsync.html> I want to use 3.0.6 because it seems that this bug: <https://bugzilla.samba.org/show_bug.cgi?id=5365> has been resolved (yay!). ----- [~]$ rsync --version rsync version 3.0.6pre1 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, file-flags ----- However, now I'm getting these kinds of messages throughout my output: ----- rsync(68321) malloc: *** error for object 0x80af80: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug deleting Desktop/PURDY/Lines of the Poet/Leonard sketch. 01.jpg rsync(68321) malloc: *** error for object 0x80af80: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug deleting Desktop/PURDY/Lines of the Poet/Leonard sketch 00.jpg rsync(68321) malloc: *** error for object 0x80af80: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug deleting Desktop/PURDY/Lines of the Poet/Leonard 03.jpg rsync(68321) malloc: *** error for object 0x80af80: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug deleting Desktop/PURDY/Lines of the Poet/Leonard 02.psd rsync(68321) malloc: *** error for object 0x80af80: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug deleting Desktop/PURDY/Lines of the Poet/Leonard 02.jpg rsync(68321) malloc: *** error for object 0x80af80: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug deleting Desktop/PURDY/Lines of the Poet/Leonard 01.jpg rsync(68321) malloc: *** error for object 0x80af80: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug deleting Desktop/PURDY/Lines of the Poet/Leanord 01.jpg ----- and not _just_ related to deleting stuff, bercause I get this too: ----- Mail Folder/Trash rsync(68157) malloc: *** error for object 0x8066b8: Non-aligned pointer being freed *** set a breakpoint in malloc_error_break to debug Spool Folder/ Spool Folder/In.temp rsync(68157) malloc: *** error for object 0x334760: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug ----- and so on. This doesn't seem to be affecting my backups at all, but I thought y'all might like to know about it. I haven't included my rsync commands, because I don't think that's what the problem is, but they're pretty much along the lines of -aNHAXvhtb --fileflages with a --backup-dir and an --exclude-from and --delete and --fake-super. I may not need the H. Thanks. -- W. Oates
On Fri, Apr 17, 2009 at 03:03:02PM -0400, Warren Oates wrote:> I compiled 3.0.6pre1, including the crtimes and fileflags patches for > use on Intel OS X 10.5.6I just compiled rsync with those patches on an Intel OS X 10.5.6 system, and didn't see any such errors. I did see an issue with "make check" (an output problem in the daemon test's file listing) which pointed me at an issue with --list-only's handling of create times. I've fixed that for the next release. Do you see free warnings for all rsync copies? What does "file rsync" say for the rsync binary? I'd suggest building your own rsync, and if the errors continue, I'll need some help to figure out what free is causing them. ..wayne..