On Wed, Jul 22, 2009 at 2:52 AM, Mac User FR wrote:
> This is a malloc (memory allocation) error.
> It shows that a non-aligned pointer (pointer that doesn't start on an
> address multiple of 4 in a 32-bit machine) is being freed. As pointers must
> always be aligned, this indicates an error and th
This is a malloc (memory allocation) error.
It shows that a non-aligned pointer (pointer that doesn't start on an
address multiple of 4 in a 32-bit machine) is being freed. As pointers
must always be aligned, this indicates an error and the function
free() doesn't know how to deal with it. B
On Mon, Jul 20, 2009 at 4:20 AM, Mark Cohen wrote:
> I too have the same issue (reported by Warren) - in that 3.06 backups appear
> valid, but the terminal shows the following errors:
>
> rsync(18819) malloc: *** error for object 0xf305c: Non-aligned pointer being
> freed
> *** set a breakpoint in
I too have the same issue (reported by Warren) - in that 3.06 backups
appear valid, but the terminal shows the following errors:
rsync(18819) malloc: *** error for object 0xf305c: Non-aligned pointer
being freed
*** set a breakpoint in malloc_error_break to debug
I'm looking for confirmatio
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.6
I 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
