> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: woensdag 10 oktober 2012 20:38
> To: Bert Huijben
> Cc: 'Johan Corveleyn'; dev_at_subversion.apache.org
> Subject: Re: crash in latest release
> On 10.10.2012 20:22, Bert Huijben wrote:
> >> -----Original Message-----
> >> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> >> Sent: woensdag 10 oktober 2012 18:40
> >> To: Johan Corveleyn
> >> Cc: dev_at_subversion.apache.org
> >> Subject: Re: crash in latest release
> >> On 09.10.2012 22:35, Johan Corveleyn wrote:
> >>> I used a release build (I always test with a release build), built
> >>> with Visual C Express 2008 on Windows XP. But indeed, it might depend
> >>> on the build ... I was probably lucky, or unlucky, depending on how
> >>> you look at it :-/ ...
> >> try this:
> >> $ svn log http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk
> >> --username=guest
> >> this will trigger the crash.
> > It doesn't trigger a crash for me. (Subversion 1.7.7 x64, SlikSvn).
> > I was also not able to crash an AnkhSVN which uses +- the same build on
> > Are you sure this is not specific to how TortoiseSVN builds Subversion or
> something like a password that was encrypted with a no longer valid key?
> Ah, now I got it:
> the crash only happens if you have saved the auth for the repo
> (tigris.org in the example above) with a different username as "guest".
> For example, I have saved the auth for tigris.org there with my username
> "steveking" so I get commit access.
> If I then pass --username=guest in a script because I only need read
> access, it crashes every time.
> So it's not as bad as I thought before.
> I guess it's only a bigger problem in case you use scripts which use
> different auth data.
Ok, with this new information (and a repository where I have access to two accounts) I can confirm that this crashes 'svn'.
I updated branches/1.7.x/STATUS in r1396944.
Received on 2012-10-11 10:40:04 CEST