RE: Assertion failure in 1.7.3

Hello,

> -----Original Message-----
> From: Perdicaro, Frank (GSB-IHPS-Corvallis)
> [mailto:frank.perdicaro_at_hp.com]
> Sent: 22 September 2012 01:06
> To: users_at_subversion.apache.org
> Subject: Assertion failure in 1.7.3
>
>
> Thanks for your work on Subversion.
> It crashed on my Win7 Pro SP1 machine (12 core Xeon5690, 48GB)
> while trying to connect for the first time to a new head.

Wow, nice system! What do you mean by "a new head"?

> My name is more than 8 chars long, so it gets remapped with a ~1.
> (The 8.3 file naming format -- with all its problems -- is
> now old enough to collect Social Security. It cannot die
> soon enough for me.)

While I agree with your comments ref 8.3, we use quite a few paths longer than 8 characters without problems (although I'm still on XP but use Win7 at home). I suspect that is not the problem.

> Of course there is no such actual directory, so we get the
> error message
>
> 'C:\Users\lngnam~1\AppData\Local\Temp' is not a working copy
>
> Then the crash:
>
> ---------------------------
> Subversion Exception!
> ---------------------------
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list

Thanks for doing this

> with as much information as possible about what
> you were trying to do.

...but this would help. What was the command(s) you tried that failed?

> But please first search the mailing list archives for the
> error message to avoid reporting the same problem repeatedly.
> You can find the mailing list archives at
> http://subversion.apache.org/mailing-lists.html

Did you do this bit? TortoiseSVN has its own mailing list too.

> Subversion reported the following
> (you can copy the content of this dialog
> to the clipboard using Ctrl-C):
>
> In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.3\ext\subversion\
subversion\libsvn_wc\wc_db.c'
> line 11679: assertion failed (svn_dirent_is_absolute(local_abspath))
> ---------------------------
> OK
> ---------------------------

Note that 1.7.3 (Dec 2011) is now 6 revisions out of date, can you try again with 1.7.9 (30th August 2012) and see if it still fails?

Cheers,

~ Mark C
Received on 2012-09-24 10:50:11 CEST