[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn merge segfaults

From: Lübbe Onken <l.onken_at_rac.de>
Date: 2003-10-17 14:25:46 CEST

Hi Folks,

I can easily make svn merge segfault by doing the following:

I've got two directories:
~/trunk = checkout from http://repos/trunk
~/branch = checkout from http://repos/branch

I'm in ~/branch and do the following:
--- SNIP ---
lonken_at_ra:~/branch > svn merge -r 365:511 https://repos/branch
A exe
Segmentation fault
lonken@ra:~/branch >
--- SNIP ---
issuing the same command in ~/trunk works like a charm :-)

Note, that the first thing svn merge is trying to do, is to add a directory
that has been created in branch and doesn't exist in rev 365 yet. I know
that when no wc is given, it defaults to '.' and merging branch into itself
doesn't make much sense (or does it?), but wouldn't it be smarter to check
whether the target has got the same url as the source instead of crashing?

The behaviour is the same on linux and on windows.

We had a similar discussion a few weeks ago on the user list: 'svn copy onto
itself is possible' where I also suggested it would be smarter if svn was
checking the target url and issue a warning, before actually doing anything.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 17 14:26:31 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.