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

Re: Bug report: Assertion failed during update/cleanup

From: Stefan Podskubka <s.podskubka_at_hcs.at>
Date: Mon, 24 Oct 2011 16:09:32 +0200

Sorry, it was too early in the morning for me to search the mailing list
archive and see that the problem was already posted a hundred times
(and, for that matter, fixed too...). Shame on me...

Anyway, the same error happens with TortoiseSVN and Subversion 1.7.1, so
is my assumption correct, that this was an error during the working copy
upgrade process from 1.6 to 1.7 and is not fixed by updating Subversion
but only by checking out a fresh working copy (or performing the upgrade
from 1.6 to 1.7 with Subversion 1.7.1, which would then result in an
error because of a corrupt working copy)?

Best regards,
Stefan

On 24.10.2011 09:27, Stefan Podskubka wrote:
> Today, when I wanted to update a working copy, I encountered the
> following assertion failure:
>
> In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\workqueue.c'
> line 672: assertion failed (checksum != NULL)
>
> Exactly the same error happened when I wanted to do a cleanup afterwards.
>
> Originally I used TortoiseSVN when this happened, but when I tried the
> cleanup with the svn.exe the same thing happened:
>
> svn: E235000: In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\workqueue.c'
> line 672: assertion failed (checksum != NULL)
>
> It happened with a working copy of sqlmap
> (https://svn.sqlmap.org/sqlmap/trunk/sqlmap), which I am using
> internally for testing SQL injections.
> The working copy was previously upgraded from version 1.6 to 1.7,
> after that I could already update the working copy multiple times
> without problems.
> When I tried to perform the update the working copy had revision 4414
> and I wanted to update to the HEAD revision, which was 4435 at that time.
> The server displays: Powered by Subversion version 1.5.1 (r32289).
> The working copy is unmodified, except one additional unversioned
> directory '/output' in the root folder of the working copy and one
> missing file '/extra/shellcodeexec/windows/shellcodeexec.x32.exe'
> (because I let my virus scanner remove it). The virus scanner also
> reports having removed the file
> '/extra/shellcodeexec/windows/.svn/text-base/shellcodeexec.x32.exe' at
> the same time, this happened before the working copy was upgraded from
> 1.6 to 1.7 and may possibly be the reason for this problem. When
> upgrading the working copy from 1.6 to 1.7 I didn't get an error.
>
> Thanks and best regards,
> Stefan
>
>
Received on 2011-10-24 16:10:14 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.