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

Subversion exception

From: Walser Markus <MarkusWalser_at_schleuniger.ch>
Date: Tue, 29 Sep 2009 12:07:24 +0200

Hi

Using Tortoise 1.6.99.17310 (snapshot 29th of September 2009) on WinXP
SP3 I encountered a subversion exception by doing the following:

1. Having a branch A with some minor local modification.
2. Merged a range of revisions from another branch B into the branch A
3. During merging I got some conflicts in branch A. (Not related to the
   local modification)
4. Aborted merge process.
5. Saved the local modification form point 1 to a patch.
6. Did a revert on the root of the branch A selecting everything.
   (containing all conflicted files and all modified files from point 1.)

I'd expected either the whole working copy to be resetted to it's base
revision or a message box requesting to do a cleanup first.

What happened was message box containg the text:

        Subversion encountered a serious problem.
        Please take the time to report this on our mailing list
        With as much information as possible about what
        you were trying to do.

        Subversion reported the following:

        In file
        'D:\Development\SVN\Releases\TortoiseSVN-1.6.5\ext\subversion\sub
      version\libsvn_wc\tree_conflicts.c'
        line 568: assertion failed (strcmp(dir_path, svn_path_dirname(
      victim_path, pool)) == 0)

Looking a bit closer to the problem I noticed, that the exception occurs
only when reverting a file with:
"Text status" = "normal, tree conflict" and "Property status" "normal".

Having "Property status" "normal" removed (happened after aborting a svn
command during debug session) revert doesn't report the exception anymore.
Instead a message box requesting a cleanup is shown.

For a call stack have a look at attachment callstack.txt.
Attachment Memory.txt contains information about variables.

The client is connected via https to a VisualSVN server version 1.6.5
with FSFS database on a Win2003 server. Is there a chance to get this
bug fixed? Can I provide something else to help solving this bug?

Kind regards,

Markus

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401557

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].

Received on 2009-09-29 12:08:45 CEST

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

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