severity 477931 important thanks serious is for debian policy violations; important is more suitable in this case.
On Fri 25 Apr 2008, Kurt Roeckx wrote: > I can consitently make rsync segfault when trying to sync the linux > kernel archive using version 3.0.2. It doesn't segfault using > 2.6.9-2etch2. This has worked for weeks but started happening yesterday. > > This is what I got from gdb: Thanks for the backtrace, very helpful. > prior_hlinks only seems to be used in case of !inc_recurse, so I > have the feeling that I shouldn't be comming there in the first place. > I'm guessing that the hashtable_find() should be inside an if (inc_recurse) > as all other hashtable_find()'s are also doing that. > > I've attached a patch that does that. It seems to be working. I'll forward it upstream so Wayne can take a look, he is very intimate with the innards of rsync :) > PS: It's annoying that when a core file gets created that it's written > in destination path instead of the directory where I started rsync. Blame Linus :-) It's what the kernel does, rsync has 0.0 influence on this besides not changing its current dir, but that would be quite suboptimal. Paul Slootman PS: sorry I haven't yet responded about your other report :-( Hope to do so soon. Real Life gets in the way sometimes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
