Segfault in 0.34.3

[Love]

"Krysak, Tony" <tony.krysak at lmco.com> writes:

> say /afs/whatever/foo.bar exists (and has > 0 size, this doesn't happen when
> the file is empty),
> do...
> cp foo.bar   foo.tmp   (works OK)
> cp foo.bar   foo.tmp   (seems to be OK)
> cp foo.bar   foo.tmp   (Segmentation fault, and foo.tmp is zero size!)  

This doesn't trigger for me.

Is it the cp or arlad that dies in a SIGSEGV ?

If its arlad, can you provide a backtrace from the coredump (or run arlad
under gdb) ?

If its the cp, can you provide a strace-log ?

Thanks,
Love