Re: Crash report

2022-09-22 Thread Pavel Lyalyakin via users
erge Chernetsov > *Cc:* users@subversion.apache.org > *Subject:* Re: Crash report > > On Thu, Sep 22, 2022 at 1:12 AM Serge Chernetsov > wrote: > > > > Hi, SVN consistently crashes (logs attached) for me every time I am > trying to commit. Could you please look into this

Re: Crash report

2022-09-22 Thread Serge Chernetsov
Thank you very much, Pavel, it resolved the issue From: Pavel Lyalyakin Sent: Thursday, September 22, 2022 04:52 To: Serge Chernetsov Cc: users@subversion.apache.org Subject: Re: Crash report On Thu, Sep 22, 2022 at 1:12 AM Serge Chernetsov wrote: > > H

Re: Crash report

2022-09-22 Thread Pavel Lyalyakin via users
On Thu, Sep 22, 2022 at 1:12 AM Serge Chernetsov wrote: > > Hi, SVN consistently crashes (logs attached) for me every time I am trying to > commit. Could you please look into this issue and maybe suggest a workaround > for me? Hello, Does the problem occur when you disable Avast antivirus or s

Re: crash report

2021-08-12 Thread Pavel Lyalyakin
Hello, Subversion 1.9 is outdated. Please, upgrade to version 1.14 and see if it helps. On Thu, Aug 12, 2021 at 11:24 AM Albert Pais wrote: > Hi, > > I was checking out a repository on an USB drive. It disconnect while > checking out. I connect the USB drive again and request for an update. SVN

Re: crash report

2015-02-20 Thread Stefan Hett
Hi Klaus, the SVN developers don't provide Windows binaries themselves. Without telling which distribution you are working with (aka: where you got the files located under C:/opt/subversion_1.7) the given dmp-file is merely useless as most likely is the given stacktrace. Regards, Stefan Fr

Re: Crash report

2014-07-14 Thread Bert Huijben
This is caused by a known issue on soms kinds of incoming deletes/replacement during merges which use --force. We recommend to stop using --force and/or upgrade to 1.8.9 where the specific problem was fixed. --force was useful on merges to avoid limitations of older subversion versions, but no

Re: crash report and minidump

2012-11-28 Thread Thorsten Schöning
Guten Tag Karla Sylvester, am Mittwoch, 28. November 2012 um 22:17 schrieben Sie: > This seem happened after I upgraded Slik-Subversion to 1.7.7 (from > 1.7.5, I believe). The same thing is happening on two different > machines, both Windows. When I do a checkout from a Linux machine, I > hav

Re: Crash report

2011-12-21 Thread Stefan Sperling
On Tue, Dec 20, 2011 at 07:04:32PM -0500, Karl Wright wrote: > Log file attached. > Karl Hi Karl, Version: 1.6.12 (SlikSvn/1.6.12) WIN32, compiled Jun 22 2010, 20:45:23 You're running a known-bad version of the SlikSvn binaries. Please upgrade. See http://svn.haxx.se/users/archive-2010-09/0065.

Re: Crash report from TortoiseSVN

2011-10-06 Thread Andy Levy
On Thu, Oct 6, 2011 at 08:26, Aleksa Todorovic wrote: > > On Thu, Oct 6, 2011 at 13:02, Andy Levy wrote: >> >> On Thu, Oct 6, 2011 at 06:22, Aleksa Todorovic wrote: >> > --- >> > Subversion Exception! >> > --- >> > Subversion encountered a serious

Re: Crash report from TortoiseSVN

2011-10-06 Thread Aleksa Todorovic
On Thu, Oct 6, 2011 at 13:02, Andy Levy wrote: > On Thu, Oct 6, 2011 at 06:22, Aleksa Todorovic wrote: > > --- > > Subversion Exception! > > --- > > Subversion encountered a serious problem. > > Please take the time to report this on the Subversion

Re: Crash report from TortoiseSVN

2011-10-06 Thread Andy Levy
On Thu, Oct 6, 2011 at 06:22, Aleksa Todorovic wrote: > --- > Subversion Exception! > --- > Subversion encountered a serious problem. > Please take the time to report this on the Subversion mailing list > (users@subversion.apache.org) > with as much

RE: crash report

2010-10-10 Thread Bert Huijben
> -Original Message- > From: lieven.govae...@gmail.com [mailto:lieven.govae...@gmail.com] On > Behalf Of Lieven Govaerts > Sent: vrijdag 8 oktober 2010 19:59 > To: Wolff, Dave > Cc: users@subversion.apache.org > Subject: Re: crash report > > On Fri, Oct 8, 2

Re: crash report

2010-10-08 Thread Lieven Govaerts
On Fri, Oct 8, 2010 at 6:32 PM, Wolff, Dave wrote: > The following happens every time I try to update a development branch to the > head of another branch.  Let me know if there’s anything I can do to help > get you more information. > This looks like the previously reported issue in sliksvn: htt