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

Re: assertion failed (opt || cstr)

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 9 Oct 2009 19:19:39 +0100

On Fri, Oct 09, 2009 at 01:54:36PM -0400, Mark Phippard wrote:
> On Fri, Oct 9, 2009 at 9:02 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> > On Thu, Oct 08, 2009 at 03:37:01PM -0600, Eduardo Kienetz wrote:
> >> Guys, I got this message today and was told to e-mail it to the dev team:
> >>
> >> In file
> >> 'D:\Development\SVN\Releases\TortoiseSVN-1.6.5\ext\subversion\subversion\libsvn_ra_svn\marshal.c'
> >>
> >> line 486: assertion failed (opt || cstr)
> >>
> >> I don't think I'll be able to reproduce though (I'm not a "pro" user, just
> >> know I was trying to reintegrate/merge a branch).
> >>
> >> I'm not subscribed to the list, so if you need to contact me please use my
> >> e-mail address.
> >
> > This is known and has been fixed.
> > The fix will be released in 1.6.6 next week.
> FWIW, I would not be so certain that the problem is "fixed". People
> have been getting that error message for years, which tells me it is
> simply the error message you get when an entire class of problems in
> the svnserve protocol happens.
> It will be great if you fixed it, but it is possible you simply fixed
> one scenario you knew about and looked at.

Well, Bert has fixed the only known way of reproducing this bug.
See http://subversion.tigris.org/issues/show_bug.cgi?id=3485
The bug was deep inside the ra_svn code. I'd say it's quite possible
that all these reports are caused by this same bug.

We cannot be sure, of course, but all we can do now is to tell people
to upgrade to 1.6.6. And should that turn out not to help all users,
we will hear about it.

I mean, what else would you do?
I guess we could phrase it as "Please try 1.6.6 and see if that helps"
if you prefer. Then again we could use this wording for *any* bug we fix.
Because the only way to know if a bug still exists is a good reproduction
recipe that triggers it. Otherwise, all we can do is assume it fixed and
hope that it will never surface again.

So let's just wait and see if these reports finally subside once enough
people have upgraded to 1.6.6.


Received on 2009-10-09 20:20:10 CEST

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.