Re: segmentation fault when moving a directory with --parents option.

Vitaly Koraykin wrote:
> Hello,
>
> i got an error and i give you the script to reproduce it.
>
> Your operating system
>
> SunOS 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Fire-V440 Solaris
>
> (rhel4) Linux 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 x86_64
> GNU/Linux
>
> (Leopard) 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT
> 2008; root:xnu-1228.7.58~1/RELEASE_I386 i386
>
> and i guess that all other
>
> The release and/or revision of Subversion
>
> svn, version 1.5.3 (r33570)
> compiled Oct 17 2008, 10:26:44
>
> The compiler and configuration options you built Subversion with
>
> i have no such information, but i know that all clients were built via
> ./configure script.
>
> Any private modifications you made to your Subversion
>
> nothing
>
> The version of Berkeley DB you're running Subversion with, if any
>
> FSFS only
>
> Anything else that could possibly be relevant. Err on the side of too much
> information, rather than too little.
>
> Steps to reproduce:
>
> on darwin:
>
> # ./get_the_bug.sh
>
> Committed revision 1.
>
> Committed revision 2.
> ./get_the_bug.sh: line 8: 1675 Bus error svn mv --parents
> --force -m "Replace d1" file://${repo}/trunk/d1 file://${repo}/trunk/d2/
> ./get_the_bug.sh: line 9: 1677 Bus error svn mv --parents
> -m "Replace d1" file://${repo}/trunk/d1 file://${repo}/trunk/d2/
>
> linux:
>
> #./get_the_bug.sh
>
> Committed revision 1.
>
> Committed revision 2.
> ./get_the_bug.sh: line 8: 12489 Segmentation fault svn mv --parents
> --force -m "Replace d1" file://${repo}/trunk/d1 file://${repo}/trunk/d2/
> ./get_the_bug.sh: line 9: 12490 Segmentation fault svn mv --parents
> -m "Replace d1" file://${repo}/trunk/d1 file://${repo}/trunk/d2/
>
> Committed revision 3.
>
> N.B. Certainly i guess that is not necessary to use --parents key in this
> case. But it will be useful in some automatic procedures.

Ouch. *any* user-generated segfault is a bug.

I couldn't find a copy of the get_the_bug.sh script you used to reproduce the
bug. Could you provide it?

Thanks,
-Hyrum