You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Eric Hanchrow <of...@blarg.net> on 2006/01/10 07:26:43 UTC
segfault in svn_wc_copy2
This is 1.3.0, which I built myself on Debian Sarge x86, configured thusly:
$ ./configure -C --prefix=/usr/local/stow/svn-1.3.x
Here's what I did:
# Change to my home directory, which is a svn working copy.
$ cd ~
# create a non-versioned file.
$ touch it
# provoke the bug.
$ svn mv --force it there
Current directory is /usr/local/stow/svn-1.3.x/bin/
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/
libthread_db.so.1".
(gdb) cd
Argument required (new working directory).
(gdb) cd ~
Working directory /home/erich.
(gdb) run mv --force it there
Starting program: /usr/local/stow/svn-1.3.x/bin/svn mv --force it there
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 8444)]
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
Program exited with code 01.
(gdb) run mv --force it there
Starting program: /usr/local/stow/svn-1.3.x/bin/svn mv --force it there
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 8446)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 8446)]
0x400361a5 in svn_wc_copy2 (src_path=0x806ba90 "it", dst_parent=0x806bc78, dst_b
asename=0x806bba8 "there", cancel_func=0x8050820 <svn_cl__check_cancel>,
cancel_baton=0x0, notify_func=0x8052850 <notify>, notify_baton=0x806bb10,
pool=0x806a6b8) at subversion/libsvn_wc/copy.c:527
(gdb) bt
#0 0x400361a5 in svn_wc_copy2 (src_path=0x806ba90 "it", dst_parent=0x806bc78, d
st_basename=0x806bba8 "there", cancel_func=0x8050820 <svn_cl__check_cancel>,
cancel_baton=0x0, notify_func=0x8052850 <notify>, notify_baton=0x806bb10,
pool=0x806a6b8) at subversion/libsvn_wc/copy.c:527
#1 0x4000fc3b in wc_to_wc_copy (src_path=0x806ba90 "it", dst_path=0x1 <Address
0x1 out of bounds>, is_move=1, force=1, ctx=0x806ab98, pool=0x806a6b8) at
subversion/libsvn_client/copy.c:158
#2 0x40011835 in setup_copy (commit_info_p=0xbffff824, src_path=0x806ba90 "it",
src_revision=0xbffff7e0, dst_path=0x806bb00 "there", is_move=1, force=0,
ctx=0x806ab98, pool=0x806a6b8) at subversion/libsvn_client/copy.c:1090
#3 0x40011c74 in svn_client_move3 (commit_info_p=0x0, src_path=0x0, dst_path=0x
0, force=0, ctx=0x0, pool=0x0) at subversion/libsvn_client/copy.c:1165
#4 0x080527c7 in svn_cl__move (os=0x0, baton=0x0, pool=0x806a6b8) at subversion
/clients/cmdline/move-cmd.c:72
#5 0x08051792 in main (argc=0, argv=0x0) at subversion/clients/cmdline/main.c:1
476
(gdb) p src_entry
$1 = (const svn_wc_entry_t *) 0x0
(gdb)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: segfault in svn_wc_copy2
Posted by Marc Sherman <ms...@projectile.ca>.
Stefan Küng wrote:
>
> Ok, recipe for TortoiseSVN:
> * inside a wc, select an unversioned file and a versioned one.
> * right-drag those files to another location in the same working copy
> * choose whatever you want from the context menu (copy or move, doesn't
> matter).
> * watch the crash.
Ah, thanks. The right-drag was the step I was missing, and it's
specific enough that a "don't do that" will work with my team.
- Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: segfault in svn_wc_copy2
Posted by Stefan Küng <to...@gmail.com>.
Marc Sherman wrote:
> Stefan Küng wrote:
>
>>That's issue #2436:
>>http://subversion.tigris.org/issues/show_bug.cgi?id=2436
>>
>>It's been fixed, and proposed for backporting to 1.3.1.
>
>
> Stefan, this is the same issue as the copy --force problem you reported
> originally against Tortoise, right? Was there a reproducible recipe
Yes, that's the same.
> using the Tortoise ui? I've tried to replicate it there, but haven't
> been able to; I'd like to know how easy it is to stumble upon in
> Tortoise so I can tell the users I support what to avoid (or if it's
> very easy to hit accidentally, suggest that they wait for 1.3.1 to upgrade).
Ok, recipe for TortoiseSVN:
* inside a wc, select an unversioned file and a versioned one.
* right-drag those files to another location in the same working copy
* choose whatever you want from the context menu (copy or move, doesn't
matter).
* watch the crash.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: segfault in svn_wc_copy2
Posted by Marc Sherman <ms...@projectile.ca>.
Stefan Küng wrote:
>
> That's issue #2436:
> http://subversion.tigris.org/issues/show_bug.cgi?id=2436
>
> It's been fixed, and proposed for backporting to 1.3.1.
Stefan, this is the same issue as the copy --force problem you reported
originally against Tortoise, right? Was there a reproducible recipe
using the Tortoise ui? I've tried to replicate it there, but haven't
been able to; I'd like to know how easy it is to stumble upon in
Tortoise so I can tell the users I support what to avoid (or if it's
very easy to hit accidentally, suggest that they wait for 1.3.1 to upgrade).
Thanks,
- Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: segfault in svn_wc_copy2
Posted by Stefan Küng <to...@gmail.com>.
Eric Hanchrow wrote:
> This is 1.3.0, which I built myself on Debian Sarge x86, configured thusly:
>
> $ ./configure -C --prefix=/usr/local/stow/svn-1.3.x
>
> Here's what I did:
>
> # Change to my home directory, which is a svn working copy.
> $ cd ~
> # create a non-versioned file.
> $ touch it
> # provoke the bug.
> $ svn mv --force it there
That's issue #2436:
http://subversion.tigris.org/issues/show_bug.cgi?id=2436
It's been fixed, and proposed for backporting to 1.3.1.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org