rsync - Jun 2005 - rsync 2.6.5 segfault using --fuzzy & --link-dest

I've been reworking my backup script & decided to give some of the newer
options a try. It would appear I've found a combination that doesn't
play nice.

$ rsync --archive --delete-during --fuzzy --hard-links --numeric-ids
 --quiet --sparse --temp-dir /backup/helium/
 --link-dest /backup/hydrogen/tuesday/
 --password-file /backup/helium/.password
 rsync://backup@helium/backup/ /backup/helium/tuesday/       
Segmentation fault

If I remove either of the --fuzzy or --link-dest options from the above command,
no more segfault. Conversely, if I remove every possible option except --fuzzy
& --link-dest, segfault every time.

You'll undoubtedly want more info to dig in further. Being that I'm
unfamiliar with gdb & strace, example usage would be helpful.

Erik

-- 
"I really want a license to do just two things: make the code available
to others, and make sure that improvements stay that way. That's really
it. Nothing more, nothing less. Everything else is fluff."
 -- Linus Torvalds

On Fri, Jun 10, 2005 at 05:14:57AM -0400, Erik Jan Tromp
wrote:
> if I remove every possible option except --fuzzy & --link-dest,
> segfault every time.
I haven't seen that in my testing.  One easy thing to do is to make sure
that core dumping is enabled and look at a backtrace:

ulimit -c unlimited
/path/to/non-stripped/rsync ...
gdb /path/to/non-stripped/rsync /path/to/core
bt

The backtract (bt) command will tell us where the program is crashing,
and should help me to find the bug.  Note that a non-stripped rsync can
be found in the build dir, and that the core file will probably be in
the destination directory of your pull transfer.

..wayne..