Re: Crash report

2022-09-22 Thread Pavel Lyalyakin via users
You are welcome! Glad to hear my suggestion helped.

On Thu, Sep 22, 2022 at 9:21 PM Serge Chernetsov 
wrote:

> 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:
> >
> > 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 set up
> antivirus exclusions?
>
> I also see that you are running the client in the downloads directory
> "C:\Users\s_a_c\Downloads\". I guess that the antivirus has some
> special handling of processes started from the downloads directory, so
> maybe starting the svn.exe client from e.g. C:\svnclient\bin\svn.exe
> could also help.
>
> I'm assuming that the problem is related to Avast because I see in the
> log that the following module is loaded:
> [[[
> 0x6fcb  C:\Program Files\Avast Software\Avast\x86\aswhook.dll
> (22.8.7500.0, 73728 bytes)
> ]]]
>
>
> --
> With best regards,
> Pavel Lyalyakin
> VisualSVN Team
>


-- 
With best regards,
Pavel Lyalyakin
VisualSVN Team


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:
>
> 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 set up
antivirus exclusions?

I also see that you are running the client in the downloads directory
"C:\Users\s_a_c\Downloads\". I guess that the antivirus has some
special handling of processes started from the downloads directory, so
maybe starting the svn.exe client from e.g. C:\svnclient\bin\svn.exe
could also help.

I'm assuming that the problem is related to Avast because I see in the
log that the following module is loaded:
[[[
0x6fcb  C:\Program Files\Avast Software\Avast\x86\aswhook.dll
(22.8.7500.0, 73728 bytes)
]]]


--
With best regards,
Pavel Lyalyakin
VisualSVN Team


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 set up
antivirus exclusions?

I also see that you are running the client in the downloads directory
"C:\Users\s_a_c\Downloads\". I guess that the antivirus has some
special handling of processes started from the downloads directory, so
maybe starting the svn.exe client from e.g. C:\svnclient\bin\svn.exe
could also help.

I'm assuming that the problem is related to Avast because I see in the
log that the following module is loaded:
[[[
0x6fcb  C:\Program Files\Avast Software\Avast\x86\aswhook.dll
(22.8.7500.0, 73728 bytes)
]]]


--
With best regards,
Pavel Lyalyakin
VisualSVN Team


Crash report

2022-09-21 Thread Serge Chernetsov
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?
<>


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
> claims for first doing a cleanup (“The working copy database at '…' is
> corrupt.”). I requested such a cleanup and I got following message.
>
> ---
>
> Subversion Exception!
>
> ---
>
> Subversion encountered a serious problem.
>
> Please take the time to report this on the Subversion mailing list
>
> with as much information as possible about what
>
> you were trying to do.
>
> 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
>
>
>
> Subversion reported the following
>
> (you can copy the content of this dialog
>
> to the clipboard using Ctrl-C):
>
>
>
> Fichier
>
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.9.7\ext\subversion\subversion\libsvn_client\cleanup.c'
>
> ligne 227 : échec de la vérification (svn_dirent_is_absolute(dir_abspath))
>
> ---
>
> OK
>
>
>
> Hop it helps !
>
>
>
> *Best regards*
>


-- 
With best regards,
Pavel Lyalyakin
VisualSVN Team


crash report

2021-08-12 Thread Albert Pais
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 claims for 
first doing a cleanup ("The working copy database at '...' is corrupt."). I 
requested such a cleanup and I got following message.
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
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

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

Fichier
'D:\Development\SVN\Releases\TortoiseSVN-1.9.7\ext\subversion\subversion\libsvn_client\cleanup.c'
ligne 227 : échec de la vérification (svn_dirent_is_absolute(dir_abspath))
---
OK

Hop it helps !

Best regards


Re: Subversion crash report

2016-01-25 Thread Stefan

Hi James,


I uninstalled the old SlikSVN, and installed the new 64-bit SlikSVN, 
using Typical installation.  Again, copied the DLLs and EXEs to 
another location for each of typing the address.  After reverting and 
cleaning up from the prior merge, I ran  the merge again.  It crashed 
at the same location as last time. Log files are included.


*From:*Stefan Hett [mailto:ste...@egosoft.com]
*Sent:* Monday, January 25, 2016 1:37 PM
*To:* Patten, James
*Cc:* 'subversion'
*Subject:* Re: Subversion crash report

Hi James,

I downloaded SlikSVN and installed it, using the Typical
installation. I then copied the DLLs and EXEs from C:\Program
Files (x86)\SlikSvn\bin to C:\MyScripts\SVN2 so that it was easier
to type the address, and ran the merge again.  It crashed.  I have
included the log files as you requested.

Thanks for the dump. Looking at the corresponding code sections 
suggest that the crash might not occur with the 64-bit binaries. Any 
chance you could try such a build? I'd expect you'd get some error in 
this case which should be a useful lead to the underlying problem.


My bad. I misread the code section there. I see why it's crashing there 
for you, but I don't know enough about the SVN source to determine the 
root cause of the issue.


I'll pass on my findings to the developers to see if they can make out 
more sense of it.


Regards,
Stefan



RE: Subversion crash report

2016-01-25 Thread Patten, James
I uninstalled the old SlikSVN, and installed the new 64-bit SlikSVN, using 
Typical installation.  Again, copied the DLLs and EXEs to another location for 
each of typing the address.  After reverting and cleaning up from the prior 
merge, I ran  the merge again.  It crashed at the same location as last time.  
Log files are included.

From: Stefan Hett [mailto:ste...@egosoft.com]
Sent: Monday, January 25, 2016 1:37 PM
To: Patten, James
Cc: 'subversion'
Subject: Re: Subversion crash report

Hi James,
I downloaded SlikSVN and installed it, using the Typical installation.  I then 
copied the DLLs and EXEs from C:\Program Files (x86)\SlikSvn\bin to 
C:\MyScripts\SVN2 so that it was easier to type the address, and ran the merge 
again.  It crashed.  I have included the log files as you requested.
Thanks for the dump. Looking at the corresponding code sections suggest that 
the crash might not occur with the 64-bit binaries. Any chance you could try 
such a build? I'd expect you'd get some error in this case which should be a 
useful lead to the underlying problem.



--

Regards,

Stefan Hett


svn-crash-log20160125134649.dmp
Description: svn-crash-log20160125134649.dmp


svn-crash-log20160125134649.log
Description: svn-crash-log20160125134649.log


Re: Subversion crash report

2016-01-25 Thread Stefan Hett

Hi James,


I downloaded SlikSVN and installed it, using the Typical 
installation.  I then copied the DLLs and EXEs from C:\Program Files 
(x86)\SlikSvn\bin to C:\MyScripts\SVN2 so that it was easier to type 
the address, and ran the merge again.  It crashed. I have included the 
log files as you requested.


Thanks for the dump. Looking at the corresponding code sections suggest 
that the crash might not occur with the 64-bit binaries. Any chance you 
could try such a build? I'd expect you'd get some error in this case 
which should be a useful lead to the underlying problem.


--
Regards,
Stefan Hett



RE: Subversion crash report

2016-01-25 Thread Patten, James
I downloaded SlikSVN and installed it, using the Typical installation.  I then 
copied the DLLs and EXEs from C:\Program Files (x86)\SlikSvn\bin to 
C:\MyScripts\SVN2 so that it was easier to type the address, and ran the merge 
again.  It crashed.  I have included the log files as you requested.

James

From: Stefan Hett [mailto:ste...@egosoft.com]
Sent: Monday, January 25, 2016 10:58 AM
To: Patten, James
Cc: 'subversion'
Subject: Re: Subversion crash report


Sorry.  I'm using the distribution from Collabnet.

From: Stefan Hett [mailto:ste...@egosoft.com]
Sent: Monday, January 25, 2016 7:30 AM
To: Patten, James
Cc: 'subversion'
Subject: Re: Subversion crash report

Hi James,
Stefan,

Windows client, using a Powershell script running the svn command line.  I am 
running 64-bit Windows 7, running it in Powershell 4.  I use the 32-bit build 
because only developers have 64-bit windows.

James

From: Stefan Hett [mailto:ste...@egosoft.com]
Sent: Monday, January 25, 2016 5:25 AM
To: Patten, James; 
users@subversion.apache.org<mailto:users@subversion.apache.org>
Subject: Re: Subversion crash report

Hi James,

without knowing which client you are using it's a bit difficult to dig into 
this problem.
>From the logs I can only get your command line, working directory, version 
>number (1.9.2) and see that you are using a 32-bit build:
Cmd line: "C:\MyScripts\SVN\svn.exe"  merge 
svn://oit-teaqasocfs1.som.w2k.state.me.us/MACWIS/branches/Verona/MACWIS 
--accept tc
Working Dir: C:\SVN_Play\z-our-server\trunk\MACWIS


Stacktrace:

#1  0x6eec60b0 in apr_file_mktemp()
#2  0x6eec66d1 in apr_file_open()
#3  0x5e55ada1 in svn_mergeinfo__filter_catalog_by_ranges()
#4  0x6eec7c2b in apr_file_read()
#5  0x6eec5d71 in apr_file_read_full()
#6  0x6dc279e3 in svn_diff_diff_2()

EAX: 0

If I were you, I'd retry the test first with the more recent 1.9.3 version.
Hello,

Attached please find a crash report during an attempt to merge something to a 
trunk.

James C Patten
Senior Programmer/Analyst, OIT OCFS/DLRS
State of Maine, Office of Information Technology
james.pat...@maine.gov<mailto:james.pat...@maine.gov>
207-557-0349 (Desk/Cell)
please always reply to the list as well, since while I might provide the first 
ideas/info, others might be better with helping with the actual problem at hand.

By "which client" I rather meant which distribution you are using. Apache 
Subversion does not provide any binaries itself, so you must be using either 
some distribution or use your own compiled binaries.

I'm asking because if the symbols would be available for the dump you provided, 
it could be easier to debug the problem.
Unfortunately I'm a bit stuck here, since I don't have access to the CollabNet 
symbol files. Maybe you can try to reproduce the issue with SilkSVN: 
https://sliksvn.com/download/ and attach the dmp file of the crash when testing 
with their version?



--

Regards,

Stefan Hett


svn-crash-log20160125114827.dmp
Description: svn-crash-log20160125114827.dmp


svn-crash-log20160125114828.log
Description: svn-crash-log20160125114828.log


Re: Subversion crash report

2016-01-25 Thread Stefan Hett



Sorry.  I’m using the distribution from Collabnet.

*From:*Stefan Hett [mailto:ste...@egosoft.com]
*Sent:* Monday, January 25, 2016 7:30 AM
*To:* Patten, James
*Cc:* 'subversion'
*Subject:* Re: Subversion crash report

Hi James,

Stefan,

Windows client, using a Powershell script running the svn command
line.  I am running 64-bit Windows 7, running it in Powershell 4. 
I use the 32-bit build because only developers have 64-bit windows.


James

*From:*Stefan Hett [mailto:ste...@egosoft.com]
*Sent:* Monday, January 25, 2016 5:25 AM
*To:* Patten, James; users@subversion.apache.org
<mailto:users@subversion.apache.org>
*Subject:* Re: Subversion crash report

Hi James,

without knowing which client you are using it's a bit difficult to
dig into this problem.
>From the logs I can only get your command line, working
directory, version number (1.9.2) and see that you are using a
32-bit build:
Cmd line: "C:\MyScripts\SVN\svn.exe"  merge
svn://oit-teaqasocfs1.som.w2k.state.me.us/MACWIS/branches/Verona/MACWIS
--accept tc
Working Dir: C:\SVN_Play\z-our-server\trunk\MACWIS


Stacktrace:

#1  0x6eec60b0 in apr_file_mktemp()
#2  0x6eec66d1 in apr_file_open()
#3  0x5e55ada1 in svn_mergeinfo__filter_catalog_by_ranges()
#4  0x6eec7c2b in apr_file_read()
#5  0x6eec5d71 in apr_file_read_full()
#6  0x6dc279e3 in svn_diff_diff_2()

EAX: 0

If I were you, I'd retry the test first with the more recent 1.9.3
version.

Hello,

Attached please find a crash report during an attempt to merge
something to a trunk.

James C Patten

Senior Programmer/Analyst, OIT OCFS/DLRS

State of Maine, Office of Information Technology

james.pat...@maine.gov <mailto:james.pat...@maine.gov>

207-557-0349 (Desk/Cell)

please always reply to the list as well, since while I might provide 
the first ideas/info, others might be better with helping with the 
actual problem at hand.


By "which client" I rather meant which distribution you are using. 
Apache Subversion does not provide any binaries itself, so you must be 
using either some distribution or use your own compiled binaries.


I'm asking because if the symbols would be available for the dump you 
provided, it could be easier to debug the problem.


Unfortunately I'm a bit stuck here, since I don't have access to the 
CollabNet symbol files. Maybe you can try to reproduce the issue with 
SilkSVN: https://sliksvn.com/download/ and attach the dmp file of the 
crash when testing with their version?


--
Regards,
Stefan Hett



RE: Subversion crash report

2016-01-25 Thread Patten, James
Sorry.  I'm using the distribution from Collabnet.

From: Stefan Hett [mailto:ste...@egosoft.com]
Sent: Monday, January 25, 2016 7:30 AM
To: Patten, James
Cc: 'subversion'
Subject: Re: Subversion crash report

Hi James,
Stefan,

Windows client, using a Powershell script running the svn command line.  I am 
running 64-bit Windows 7, running it in Powershell 4.  I use the 32-bit build 
because only developers have 64-bit windows.

James

From: Stefan Hett [mailto:ste...@egosoft.com]
Sent: Monday, January 25, 2016 5:25 AM
To: Patten, James; 
users@subversion.apache.org<mailto:users@subversion.apache.org>
Subject: Re: Subversion crash report

Hi James,

without knowing which client you are using it's a bit difficult to dig into 
this problem.
>From the logs I can only get your command line, working directory, version 
>number (1.9.2) and see that you are using a 32-bit build:
Cmd line: "C:\MyScripts\SVN\svn.exe"  merge 
svn://oit-teaqasocfs1.som.w2k.state.me.us/MACWIS/branches/Verona/MACWIS 
--accept tc
Working Dir: C:\SVN_Play\z-our-server\trunk\MACWIS


Stacktrace:

#1  0x6eec60b0 in apr_file_mktemp()
#2  0x6eec66d1 in apr_file_open()
#3  0x5e55ada1 in svn_mergeinfo__filter_catalog_by_ranges()
#4  0x6eec7c2b in apr_file_read()
#5  0x6eec5d71 in apr_file_read_full()
#6  0x6dc279e3 in svn_diff_diff_2()

EAX: 0

If I were you, I'd retry the test first with the more recent 1.9.3 version.
Hello,

Attached please find a crash report during an attempt to merge something to a 
trunk.

James C Patten
Senior Programmer/Analyst, OIT OCFS/DLRS
State of Maine, Office of Information Technology
james.pat...@maine.gov<mailto:james.pat...@maine.gov>
207-557-0349 (Desk/Cell)
please always reply to the list as well, since while I might provide the first 
ideas/info, others might be better with helping with the actual problem at hand.

By "which client" I rather meant which distribution you are using. Apache 
Subversion does not provide any binaries itself, so you must be using either 
some distribution or use your own compiled binaries.

I'm asking because if the symbols would be available for the dump you provided, 
it could be easier to debug the problem.



--

Regards,

Stefan Hett


Re: Subversion crash report

2016-01-25 Thread Stefan Hett

Hi James,


Stefan,

Windows client, using a Powershell script running the svn command 
line.  I am running 64-bit Windows 7, running it in Powershell 4.  I 
use the 32-bit build because only developers have 64-bit windows.


James

*From:*Stefan Hett [mailto:ste...@egosoft.com]
*Sent:* Monday, January 25, 2016 5:25 AM
*To:* Patten, James; users@subversion.apache.org
*Subject:* Re: Subversion crash report

Hi James,

without knowing which client you are using it's a bit difficult to dig 
into this problem.
>From the logs I can only get your command line, working directory, 
version number (1.9.2) and see that you are using a 32-bit build:
Cmd line: "C:\MyScripts\SVN\svn.exe"  merge 
svn://oit-teaqasocfs1.som.w2k.state.me.us/MACWIS/branches/Verona/MACWIS --accept 
tc

Working Dir: C:\SVN_Play\z-our-server\trunk\MACWIS


Stacktrace:

#1  0x6eec60b0 in apr_file_mktemp()
#2  0x6eec66d1 in apr_file_open()
#3  0x5e55ada1 in svn_mergeinfo__filter_catalog_by_ranges()
#4  0x6eec7c2b in apr_file_read()
#5  0x6eec5d71 in apr_file_read_full()
#6  0x6dc279e3 in svn_diff_diff_2()

EAX: 0

If I were you, I'd retry the test first with the more recent 1.9.3 
version.


Hello,

Attached please find a crash report during an attempt to merge
something to a trunk.

James C Patten

Senior Programmer/Analyst, OIT OCFS/DLRS

State of Maine, Office of Information Technology

james.pat...@maine.gov <mailto:james.pat...@maine.gov>

207-557-0349 (Desk/Cell)

please always reply to the list as well, since while I might provide the 
first ideas/info, others might be better with helping with the actual 
problem at hand.


By "which client" I rather meant which distribution you are using. 
Apache Subversion does not provide any binaries itself, so you must be 
using either some distribution or use your own compiled binaries.


I'm asking because if the symbols would be available for the dump you 
provided, it could be easier to debug the problem.


--
Regards,
Stefan Hett



Re: Subversion crash report

2016-01-25 Thread Stefan Hett

Hi James,

without knowing which client you are using it's a bit difficult to dig 
into this problem.
From the logs I can only get your command line, working directory, 
version number (1.9.2) and see that you are using a 32-bit build:
Cmd line: "C:\MyScripts\SVN\svn.exe"  merge 
svn://oit-teaqasocfs1.som.w2k.state.me.us/MACWIS/branches/Verona/MACWIS 
--accept tc

Working Dir: C:\SVN_Play\z-our-server\trunk\MACWIS


Stacktrace:

#1  0x6eec60b0 in apr_file_mktemp()
#2  0x6eec66d1 in apr_file_open()
#3  0x5e55ada1 in svn_mergeinfo__filter_catalog_by_ranges()
#4  0x6eec7c2b in apr_file_read()
#5  0x6eec5d71 in apr_file_read_full()
#6  0x6dc279e3 in svn_diff_diff_2()

EAX: 0

If I were you, I'd retry the test first with the more recent 1.9.3 version.


Hello,

Attached please find a crash report during an attempt to merge 
something to a trunk.


James C Patten

Senior Programmer/Analyst, OIT OCFS/DLRS

State of Maine, Office of Information Technology

james.pat...@maine.gov <mailto:james.pat...@maine.gov>

207-557-0349 (Desk/Cell)




--
Regards,
Stefan Hett



Subversion crash report

2016-01-24 Thread Patten, James
Hello,

Attached please find a crash report during an attempt to merge something to a 
trunk.

James C Patten
Senior Programmer/Analyst, OIT OCFS/DLRS
State of Maine, Office of Information Technology
james.pat...@maine.gov<mailto:james.pat...@maine.gov>
207-557-0349 (Desk/Cell)




svn-crash-log20160122130829.dmp
Description: svn-crash-log20160122130829.dmp


svn-crash-log20160122130829.log
Description: svn-crash-log20160122130829.log


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


Freundliche Grüße / kind regards

i. A. Dipl.-Phys. Klaus Rezepka

Entwicklung Powertrain



Lauer & Weiss GmbH
Kompetenzzentrum für Modulentwicklung
Höhenstraße 21
70736 Fellbach
Tel: +49 711 520889 259
Fax: +49 711 520889 20
Mail: klaus.reze...@lauer-weiss.de 
www.lauer-weiss.de 

Geschäftsführer: Jochen Lauer
Bankverbindung: IBAN: DE25 6026 1329 0032 8800 06  BIC: GENODES1FBB
Umsatzregister: ID-Nr. DE 210208516
Registergericht: Amtsgericht Stuttgart
Registernummer: HRB Nr. 264166






crash report

2015-02-20 Thread Rezepka, Klaus


Freundliche Gr??e / kind regards

i. A. Dipl.-Phys. Klaus Rezepka

Entwicklung Powertrain

[cid:luw_logo6a3f87]

Lauer & Weiss GmbH
Kompetenzzentrum f?r Modulentwicklung
H?henstra?e 21
70736 Fellbach
Tel: +49 711 520889 259
Fax: +49 711 520889 20
Mail: klaus.reze...@lauer-weiss.de
www.lauer-weiss.de

Gesch?ftsf?hrer: Jochen Lauer
Bankverbindung: IBAN: DE25 6026 1329 0032 8800 06  BIC: GENODES1FBB
Umsatzregister: ID-Nr. DE 210208516
Registergericht: Amtsgericht Stuttgart
Registernummer: HRB Nr. 264166



svn-crash-log20150219181014.dmp
Description: svn-crash-log20150219181014.dmp


svn-crash-log20150219181014.log
Description: svn-crash-log20150219181014.log


Subversion crash report

2014-11-05 Thread Jesse Farnham
This occurred while running an svn merge from trunk to a branch.



Disclaimer: This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient or have received this e-mail in error, 
please notify the sender immediately and destroy/delete this e-mail. You are 
hereby notified that any unauthorized copying, disclosure or distribution of 
the material in this e-mail is strictly prohibited.

This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All information contained in 
this communication is not warranted as to completeness or accuracy and is 
subject to change without notice. Any comments or statements made in this 
communication do not necessarily reflect those of AQR Capital Management, LLC 
and its affiliates.


svn-crash-log20141105162102.dmp
Description: svn-crash-log20141105162102.dmp


svn-crash-log20141105162102.log
Description: svn-crash-log20141105162102.log


Re: svn crash report

2014-07-22 Thread Johan Corveleyn
On Sat, Jul 19, 2014 at 7:58 AM, ayush Mittal  wrote:
> Attaching crash report while downloading trunk

Did you compile your own svn binary for Windows? If so, I suggest you first
try one of the freely available binary packages, and see if you can
replicate the issue.

See http://subversion.apache.org/packages.html#windows.

-- 
Johan


svn crash report

2014-07-20 Thread ayush Mittal
Attaching crash report while downloading trunk

svn-crash-log20140719111932.log
Description: Binary data


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 now it just disables some cases of proper tree conflict detection.


Bert






Sent from Windows Mail





From: Oryl, Michael
Sent: ‎Monday‎, ‎July‎ ‎14‎, ‎2014 ‎3‎:‎50‎ ‎PM
To: users@subversion.apache.org





This was an attempt to merge a single revision from a branch to the trunk.  It 
was the revision that created the branch.

The branch had been made from a working copy that had local changes already 
when the branch was being created.  Basically I didn't want to commit the local 
changes to trunk, so I made a new branch from the working copy.

The change was initiated from within JetBrains' IntelliJ IDEA 13.1.3.

This message, including any attachments, is intended only for the recipient(s) 
named above. It may contain confidential and privileged information. If you 
have received this communication in error, please notify the sender immediately 
and destroy or delete the original message. Also, please be aware that if you 
are not the intended recipient, any review, disclosure, copying, distribution 
or any action or reliance based on this message is prohibited by law.

Re: Subversion crash report

2013-03-13 Thread Thorsten Schöning
Guten Tag Zhu Bicen,
am Mittwoch, 13. März 2013 um 00:40 schrieben Sie:

> Could you please check?  Thanks!

http://svn.haxx.se/users/archive-2012-10/0099.shtml

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow



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 
> have no problem.

http://mail-archives.apache.org/mod_mbox/subversion-users/201211.mbox/%3c20121104101302.gd27...@ted.stsp.name%3E

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow



crash report and minidump

2012-11-28 Thread Karla Sylvester
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 
have no problem.


Thanks for the help,

--
Karla Sylvester
Senior Software Engineer
Wegmann USA, Inc
Training & Simulation
Office: 407-381-6004



svn-crash-log20121128160202.dmp
Description: Binary data

Process info:
Cmd line: "C:/Program Files/SlikSvn/bin/svn.exe" checkout --username Karla 
http://71.46.229.226:8181/svn/sysmanager/sysmanager-agent/trunk sysmanager-agent
Working Dir: C:\workspace\buildsystem
Version:  1.7.7-SlikSvn-1.7.7-X64 (SlikSvn/1.7.7) X64, compiled Oct  9 2012, 
15:02:20
Platform: Windows OS version 6.1 build 7601 Service Pack 1

Exception: ACCESS_VIOLATION

Registers:
Rax= Rcx= Rdx= 
Rbx=002cee34
Rsp=002ced70 Rbp=002cee38 Rsi=005c0038 
Rdi=
R8=  R9= fffd1c50 R10= 77c87c50 
R11=004ebae0
R12= R13=005c0038 R14=00626870 
R15=002cef10
cs=0033  ss=002b  ds=002b  es=0053  fs=002b  gs=002b  ss=0094

Stacktrace:
#1  0x7fb7127 in svn_auth_get_username_prompt_provider()
#2  0x7fb3a7f in svn_auth_get_platform_specific_client_providers()
#3  0x7fb7235 in svn_auth_get_username_prompt_provider()
#4  0x7fb2f20 in svn_auth_first_credentials()
#5  0x7feee834583 in svn_ra_local_init()
#6  0x7feee875be0 in svn_ra_get_ra_library()
#7  0x7feee87526c in svn_ra_get_ra_library()
#8  0x7feee8757ef in svn_ra_get_ra_library()
#9  0x7feee87801a in svn_ra_get_ra_library()
#10  0x7feee8780b9 in svn_ra_get_ra_library()
#11  0x7feee845c05 in svn_ra_dav_init()
#12  0x7feee837db9 in svn_ra_dav_init()
#13  0x7feee835b3c in svn_ra_local_init()
#14  0x7feee86cb55 in svn_ra_open4()
#15  0x7fef676e134 in svn_client_suggest_merge_sources()
#16  0x7fef676f11b in svn_client_uuid_from_path2()
#17  0x7fef674a785 in svn_client_cat2()
#18  0x7fef674ab99 in svn_client_checkout3()
#19  0x13f2f2338 in (unknown function)
#20  0x13f2fa44a in (unknown function)
#21  0x13f3047ee in (unknown function)
#22  0x775e652d in BaseThreadInitThunk()
#23  0x77b7c521 in RtlUserThreadStart()


Loaded modules:
0x3f2f  C:\Program Files\SlikSvn\bin\svn.exe (1.7.7.17343, 241664 bytes)
0x77b5  C:\Windows\System32\ntdll.dll (6.1.7601.17725, 1740800 bytes)
0x775d  C:\Windows\System32\kernel32.dll (6.1.7601.17932, 1175552 bytes)
0xfe27  C:\Windows\System32\KERNELBASE.dll (6.1.7601.17932, 442368 bytes)
0x6eec  C:\Program Files\SlikSvn\bin\SlikSvn-libintl-x64.dll (0.0.0.0, 
61440 bytes)
0x71a5  
C:\Windows\winsxs\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\msvcr90.dll
 (9.0.30729.6161, 667648 bytes)
0x000e  C:\Program Files\SlikSvn\bin\SlikSvn-libapr-1.dll (1.4.6.0, 184320 
bytes)
0xff9f  C:\Windows\System32\ws2_32.dll (6.1.7601.17514, 315392 bytes)
0xff61  C:\Windows\System32\msvcrt.dll (7.0.7601.17744, 651264 bytes)
0xff84  C:\Windows\System32\rpcrt4.dll (6.1.7601.17514, 1232896 bytes)
0xff75  C:\Windows\System32\nsi.dll (6.1.7600.16385, 32768 bytes)
0xfd76  C:\Windows\System32\mswsock.dll (6.1.7601.17514, 348160 bytes)
0x77a5  C:\Windows\System32\user32.dll (6.1.7601.17514, 1024000 bytes)
0xff3b  C:\Windows\System32\gdi32.dll (6.1.7601.17514, 421888 bytes)
0xffe5  C:\Windows\System32\lpk.dll (6.1.7600.16385, 57344 bytes)
0xfe42  C:\Windows\System32\usp10.dll (1.626.7601.17561, 823296 bytes)
0xff42  C:\Windows\System32\advapi32.dll (6.1.7600.16385, 897024 bytes)
0xfe4f  C:\Windows\System32\sechost.dll (6.1.7600.16385, 126976 bytes)
0xfe62  C:\Windows\System32\shell32.dll (6.1.7601.17859, 14188544 bytes)
0xff7c  C:\Windows\System32\shlwapi.dll (6.1.7601.17514, 462848 bytes)
0xf674  C:\Program Files\SlikSvn\bin\SlikSvn-svn_client-1.dll (1.7.7.17343, 
352256 bytes)
0x6ee6  C:\Program Files\SlikSvn\bin\SlikSvn-libaprutil-1.dll (1.5.1.0, 
258048 bytes)
0xf90d  C:\Program Files\SlikSvn\bin\SlikSvn-svn_delta-1.dll (1.7.7.17343, 
110592 bytes)
0xeeeb  C:\Program Files\SlikSvn\bin\SlikSvn-svn_subr-1.dll (1.7.7.17343, 
958464 bytes)
0xffc4  C:\Windows\System32\ole32.dll (6.1.7601.17514, 2109440 bytes)
0xfe06  C:\Windows\System32\crypt32.dll (6.1.7601.17856, 1482752 bytes)
0xfe05  C:\Windows\System32\msasn1.dll (6.1.7601.17514, 61440 bytes)
0xf8bf  C:\Program Files\SlikSvn\bin\SlikSvn-svn_diff-1.dll (1.7.7.17343, 
86016 bytes)
0xee83  C:\Program Files\SlikSvn\bin\SlikSvn-svn_ra-1.dll (1.7.7.17343, 
532480 bytes)
0xf669  C:\Program Files\SlikSvn\bin\SlikSvn-svn_repos-1.dll (1.7.7.17343, 
196608 bytes)
0xf13e  C:\Program Files\SlikSvn\bin\SlikSvn-svn_fs-1.dll (1.7.7.17343, 
323584 bytes)
0x1300  C:\Program Files\SlikSvn\bin\SlikSvn-DB44-20-x64.dll (4.0.4.20, 
933888 bytes)
0x6ec6  
C:\Windows\winsxs\amd64_micros

Re: This application has halted due to an unexpected error. A crash report and minidump file were saved to disk

2012-11-08 Thread Stefan Sperling
On Thu, Nov 08, 2012 at 11:40:08PM +0200, Sergey Chekotilo wrote:
> Thanks and Regards
> Sergey Chekotilo

This is a known bug in 1.7.7 which happens only on Windows.
Due to a coding error, when a user name is already cached and
the --username option specifies a different user name than the
one in the cache, svn crashes.

If this affects you and you cannot work around it I'd recommended 
using 1.7.6 until 1.7.8 gets released which will include a fix.


This application has halted due to an unexpected error. A crash report and minidump file were saved to disk

2012-11-08 Thread Sergey Chekotilo
-- 
__
Thanks and Regards
Sergey Chekotilo
Cell:+380913194550


svn-crash-log20121108233205.dmp
Description: Binary data


svn-crash-log20121108233205.log
Description: Binary data


Re: SVN crash report

2012-11-04 Thread Stefan Sperling
On Sat, Nov 03, 2012 at 11:12:53PM +0200, Ivan Cenov wrote:
> Hello,
> 
> Here I send you a crash report in SVN.
> This crash occurs when Redmine (project management application)
> tries to fetch revisions for SVN repositories.

This is a known bug in 1.7.7 which happens only on Windows.
Due to a coding error, when a user name is already cached and
the --username option specifies a different user name than the
one in the cache, svn crashes.

If this affects you and you cannot work around it I'd recommended
using 1.7.6 until 1.7.8 gets released which will include a fix.


SVN crash report

2012-11-03 Thread Ivan Cenov

Hello,

Here I send you a crash report in SVN.
This crash occurs when Redmine (project management application)
tries to fetch revisions for SVN repositories.

--
Regards,

Ivan Cenov
OKTO-7 Co. Bulgaria
i...@okto7.com, i_ce...@botevgrad.com
mobile:+359888761080,
phone:+35972366161, fax:+_35972366262



svn-crash-log20121103223521.dmp
Description: Binary data

Process info:
Cmd line: "C:\Program Files\csvn\bin\svn.exe" info --xml 
"http://repos.ourcompany.com/lib/svn/PIC16T_1822//"; --username "redmine" 
--password "redminepwd" --no-auth-cache --non-interactive
Working Dir: E:\data\redmine
Version:  1.7.7 (r1393599), compiled Oct 12 2012, 00:25:56
Platform: Windows OS version 5.2 build 3790 Service Pack 2

Exception: ACCESS_VIOLATION

Registers:
Rax= Rcx= Rdx= 
Rbx=0023f094
Rsp=0023efd0 Rbp=0023f0a8 Rsi=02416018 
Rdi=
R8=  R9= ffd25130 R10= 04fbe21c0001 
R11=02416018
R12=0001 R13=02454518 R14=02416018 
R15=02453820
cs=0033  ss=002b  ds=002b  es=0053  fs=002b  gs=002b  ss=0094

Stacktrace:
#1  0x004c7847 in svn_auth_get_username_prompt_provider()
#2  0x004c3bb2 in svn_auth_get_platform_specific_client_providers()
#3  0x004c7955 in svn_auth_get_username_prompt_provider()
#4  0x004c2be1 in svn_auth_first_credentials()
#5  0x00684093 in svn_ra_local_init()
#6  0x006c8080 in svn_ra_get_ra_library()
#7  0x006c751b in svn_ra_get_ra_library()
#8  0x006c7a9f in svn_ra_get_ra_library()
#9  0x006ca84a in svn_ra_get_ra_library()
#10  0x006ca9c4 in svn_ra_get_ra_library()
#11  0x006963f5 in svn_ra_dav_init()
#12  0x00687979 in svn_ra_dav_init()
#13  0x00685656 in svn_ra_local_init()
#14  0x006be9ef in svn_ra_open4()
#15  0x18002d463 in svn_client_suggest_merge_sources()
#16  0x18002e35d in svn_client_uuid_from_path2()
#17  0x1800186a6 in svn_client_info3()
#18  0x140005c08 in (unknown function)
#19  0x1400090bd in (unknown function)
#20  0x14001233e in (unknown function)
#21  0x77d5965c in BaseProcessStart()


Loaded modules:
0x4000  C:\Program Files\csvn\bin\svn.exe (1.7.7.17343, 233472 bytes)
0x77ec  C:\WINDOWS\system32\ntdll.dll (5.2.3790.4455, 1290240 bytes)
0x77d4  C:\WINDOWS\system32\kernel32.dll (5.2.3790.4480, 1531904 bytes)
0x6eec  C:\Program Files\csvn\bin\libapr-1.dll (1.4.6.0, 172032 bytes)
0x7731  C:\WINDOWS\system32\ws2_32.dll (5.2.3790.3959, 196608 bytes)
0x7fc0  C:\WINDOWS\system32\msvcrt.dll (7.0.3790.4400, 548864 bytes)
0x7714  C:\WINDOWS\system32\ws2help.dll (5.2.3790.1830, 49152 bytes)
0x7fee  C:\WINDOWS\system32\advapi32.dll (5.2.3790.4497, 1085440 bytes)
0x7fd3  C:\WINDOWS\system32\rpcrt4.dll (5.2.3790.4502, 1699840 bytes)
0x7e9c  C:\WINDOWS\system32\secur32.dll (5.2.3790.4455, 139264 bytes)
0x771b  C:\WINDOWS\system32\mswsock.dll (5.2.3790.4318, 512000 bytes)
0x7f19  C:\WINDOWS\system32\shell32.dll (6.0.3790.4423, 10530816 bytes)
0x7fc9  C:\WINDOWS\system32\gdi32.dll (5.2.3790.4516, 638976 bytes)
0x77c2  C:\WINDOWS\system32\user32.dll (5.2.3790.4033, 1097728 bytes)
0x7ef6  C:\WINDOWS\system32\shlwapi.dll (6.0.3790.4235, 634880 bytes)
0x7973  C:\Program Files\csvn\bin\MSVCR100.DLL (10.0.30319.460, 856064 
bytes)
0x8000  C:\Program Files\csvn\bin\libsvn_client-1.dll (1.7.7.17343, 450560 
bytes)
0x6ee6  C:\Program Files\csvn\bin\libaprutil-1.dll (1.4.1.0, 229376 bytes)
0x6ee5  C:\Program Files\csvn\bin\libapriconv-1.dll (1.2.1.0, 53248 bytes)
0x0048  C:\Program Files\csvn\bin\libsvn_delta-1.dll (1.7.7.17343, 163840 
bytes)
0x004c  C:\Program Files\csvn\bin\libsvn_subr-1.dll (1.7.7.17343, 1527808 
bytes)
0x7daa  C:\WINDOWS\system32\shfolder.dll (6.0.3790.1830, 49152 bytes)
0x5714  C:\WINDOWS\system32\ole32.dll (5.2.3790.4428, 2646016 bytes)
0x7d37  C:\WINDOWS\system32\crypt32.dll (5.131.3790.4477, 1437696 bytes)
0x7d34  C:\WINDOWS\system32\msasn1.dll (5.2.3790.3959, 172032 bytes)
0x0065  C:\Program Files\csvn\bin\libsvn_diff-1.dll (1.7.7.17343, 122880 
bytes)
0x0068  C:\Program Files\csvn\bin\libsvn_ra-1.dll (1.7.7.17343, 884736 
bytes)
0x0077  C:\Program Files\csvn\bin\libeay32.dll (1.0.0.10, 1589248 bytes)
0x0090  C:\Program Files\csvn\bin\ssleay32.dll (1.0.0.10, 319488 bytes)
0x0095  C:\Program Files\csvn\bin\libsvn_fs-1.dll (1.7.7.17343, 262144 
bytes)
0x009a  C:\Program Files\csvn\bin\libsvn_repos-1.dll (1.7.7.17343, 253952 
bytes)
0x009f  C:\Program Files\csvn\bin\libsvn_wc-1.dll (1.7.7.17343, 708608 
bytes)
0x7d50  C:\WINDOWS\system32\imm32.dll (5.2.3790.3959, 233472 bytes)
0x0239  C:\Program Files\Prio\prio.dll (1.9.9.1732, 28672 bytes)
0x7f00  
C:\WINDOWS\WinSxS\amd64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_0A7B2435\comctl32.dll
 (6.0.3790.3959, 1601536 bytes)
0x7753  C:\WINDOWS\system32\security.dll (5.2.3790.1

RE: TortoiseSVN crash report (cleanup failed)

2012-01-29 Thread Ng, Alan
Additional information: I discovered that the root of the problem was that
at some point in the past (months ago) the SourceForge repository got *both*
a lowercase and an uppercase version of the same filename. On Macs, svn
brought down only the uppercase file. On Windows XP, TortoiseSVN brought
down only the lowercase file. Presumably commits from both machines over
time got everything all mucked up.

This does suggest that some improvement could be made in SVN regarding
committing filenames differing only in case from what's already in the
repository.

> -Original Message-
> From: Ng, Alan
> Sent: Friday, January 27, 2012 2:19 PM
> To: 'users@subversion.apache.org'
> Subject: TortoiseSVN crash report (cleanup failed)
> 
> As far as I can tell, the repository on this machine (which generated the
> error message copied below) got confused at some point in the past about
> upper/lowercase on one filename. My SourceForge repository has the
filename
> all in lowercase, whereas this Windows machine had the corresponding file
in
> uppercase. My attempts on this machine to synchronize or update the local
> repository with the SF repository failed. When I then manually deleted the
> Window file and attempted to synchronize or update, then SVN asks me to
run
> cleanup first. Clean up attempts (involving the folder which had the
offending
> uppercase file) then fail with this message:
> 
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as much information as possible about what
> you were trying to do.
> 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
> 
> 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.4\ext\subversion\subversion\libsvn_wc\workqueue.c' line 673: assertion
> failed (checksum !=
NULL)---OK---


smime.p7s
Description: S/MIME cryptographic signature


TortoiseSVN crash report (cleanup failed)

2012-01-29 Thread Ng, Alan
As far as I can tell, the repository on this machine (which generated the 
error message copied below) got confused at some point in the past about 
upper/lowercase on one filename. My SourceForge repository has the filename 
all in lowercase, whereas this Windows machine had the corresponding file in 
uppercase. My attempts on this machine to synchronize or update the local 
repository with the SF repository failed. When I then manually deleted the 
Window file and attempted to synchronize or update, then SVN asks me to run 
cleanup first. Clean up attempts (involving the folder which had the offending 
uppercase file) then fail with this message:

---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
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

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.4\ext\subversion\subversion\libsvn_wc\workqueue.c'
 line 673: assertion failed (checksum != 
NULL)---OK---

smime.p7s
Description: S/MIME cryptographic signature


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.shtml


Crash report

2011-12-20 Thread Karl Wright
Log file attached.
Karl


svn-crash-log20111220190155.log
Description: Binary data


Crash report

2011-10-24 Thread Markus Gagliardi
I tried a svn cleanup from the Explorer Shell.

Best regards
Markus Gagliardi

---
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 information as possible about what
you were trying to do.
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

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.0\ext\subversion\subversion
\libsvn_wc\wc_db.c'
 line 9465: assertion failed (work_presence == svn_wc__db_status_normal
||
 work_presence == svn_wc__db_status_not_present || work_presence ==
 svn_wc__db_status_base_deleted)
---
OK   
---


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 problem.
>> > Please take the time to report this on the Subversion mailing list
>> > (users@subversion.apache.org)
>> > with as much information as possible about what
>> > you were trying to do.
>> > 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
>> >
>> > Subversion reported the following
>> > (you can copy the content of this dialog
>> > to the clipboard using Ctrl-C):
>> >
>> > In file
>> >
>> > 'C:\Users\kueng\nightlybuilds\latest\TortoiseSVN\ext\subversion\subversion\libsvn_subr\dirent_uri.c'
>> > line 1596: assertion failed (! svn_path_is_url(relative))
>> > ---
>> > OK
>> > ---
>> >
>> > I'm on Windows XP, TortoiseSVN 1.6.99, build 22019 - 32bit dev -
>> > 2011/09/22
>> > 12:01:54
>> > Subversion 1.7.0 -dev
>> > apr 1.4.5
>> > apr-utils 1.3.12
>> > neon 0.29.6
>> > OpenSSL 1.0.0d 9 Feb 2011
>> > zlib 1.2.5
>> > Steps for the crash:
>> > 1. I opened Show Log dialog on my checkout
>> > 2. Selected last revesion (I committed it)
>> > 3. Right-clicked on the file I committed (only on file was in commit),
>> > and
>> > chose "Revert changes from this revision"
>> > 4. There happens crash!
>> > Hope this helps
>>
>> Please try with the latest nightly build of TortoiseSVN and/or the
>> latest Subversion. Your build is 2 weeks old.
>
> Tried with lates nightly build (r22055), it still crashes. Can you (or
> someone else) point me to Windows svn nightly build binaries so I can try
> with them?

Stefan has builds available alongside the TSVN builds.
http://nightlybuilds.tortoisesvn.net/latest/win32/full/


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 mailing list
> > (users@subversion.apache.org)
> > with as much information as possible about what
> > you were trying to do.
> > 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
> >
> > Subversion reported the following
> > (you can copy the content of this dialog
> > to the clipboard using Ctrl-C):
> >
> > In file
> >
> 'C:\Users\kueng\nightlybuilds\latest\TortoiseSVN\ext\subversion\subversion\libsvn_subr\dirent_uri.c'
> > line 1596: assertion failed (! svn_path_is_url(relative))
> > ---
> > OK
> > ---
> >
> > I'm on Windows XP, TortoiseSVN 1.6.99, build 22019 - 32bit dev -
> 2011/09/22
> > 12:01:54
> > Subversion 1.7.0 -dev
> > apr 1.4.5
> > apr-utils 1.3.12
> > neon 0.29.6
> > OpenSSL 1.0.0d 9 Feb 2011
> > zlib 1.2.5
> > Steps for the crash:
> > 1. I opened Show Log dialog on my checkout
> > 2. Selected last revesion (I committed it)
> > 3. Right-clicked on the file I committed (only on file was in commit),
> and
> > chose "Revert changes from this revision"
> > 4. There happens crash!
> > Hope this helps
>
> Please try with the latest nightly build of TortoiseSVN and/or the
> latest Subversion. Your build is 2 weeks old.
>

Tried with lates nightly build (r22055), it still crashes. Can you (or
someone else) point me to Windows svn nightly build binaries so I can try
with them?


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 information as possible about what
> you were trying to do.
> 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
>
> Subversion reported the following
> (you can copy the content of this dialog
> to the clipboard using Ctrl-C):
>
> In file
> 'C:\Users\kueng\nightlybuilds\latest\TortoiseSVN\ext\subversion\subversion\libsvn_subr\dirent_uri.c'
> line 1596: assertion failed (! svn_path_is_url(relative))
> ---
> OK
> ---
>
> I'm on Windows XP, TortoiseSVN 1.6.99, build 22019 - 32bit dev - 2011/09/22
> 12:01:54
> Subversion 1.7.0 -dev
> apr 1.4.5
> apr-utils 1.3.12
> neon 0.29.6
> OpenSSL 1.0.0d 9 Feb 2011
> zlib 1.2.5
> Steps for the crash:
> 1. I opened Show Log dialog on my checkout
> 2. Selected last revesion (I committed it)
> 3. Right-clicked on the file I committed (only on file was in commit), and
> chose "Revert changes from this revision"
> 4. There happens crash!
> Hope this helps

Please try with the latest nightly build of TortoiseSVN and/or the
latest Subversion. Your build is 2 weeks old.


Crash report from TortoiseSVN

2011-10-06 Thread Aleksa Todorovic
---
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 information as possible about what
you were trying to do.
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

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

In file
'C:\Users\kueng\nightlybuilds\latest\TortoiseSVN\ext\subversion\subversion\libsvn_subr\dirent_uri.c'
line 1596: assertion failed (! svn_path_is_url(relative))
---
OK
---

I'm on Windows XP, TortoiseSVN 1.6.99, build 22019 - 32bit dev - 2011/09/22
12:01:54
Subversion 1.7.0 -dev
apr 1.4.5
apr-utils 1.3.12
neon 0.29.6
OpenSSL 1.0.0d 9 Feb 2011
zlib 1.2.5

Steps for the crash:
1. I opened Show Log dialog on my checkout
2. Selected last revesion (I committed it)
3. Right-clicked on the file I committed (only on file was in commit), and
chose "Revert changes from this revision"
4. There happens crash!

Hope this helps


Re: subversion crash report

2011-03-17 Thread R. Cody Erben
On Mar 16, 2011, at 16:33 , Lieven Govaerts wrote:

> On Wed, Mar 16, 2011 at 11:08 PM, Ryan Schmidt
>  wrote:
>> 
>> On Mar 16, 2011, at 14:20, Darryl Fenwick wrote:
>>> My subversion (version 1.6.15) on my 64-bit windows 7 machine has been 
>>> unstable.  I get a lot of complaints about not being able to copy files 
>>> from the tmp directory, etc, when I try to update.
>>> 
> 
> What type of complaints?

This sounds like an issue with Windows 7, the indexing service and/or 
anti-virus, and Subversion's usage of temp files. This issue has a hotfix 
available, and I have been running Win7 w/ the indexing server re-enabled on 
SP1 without a hitch for a week or so now.  More information and links to the 
hotfix:

http://subversion.wandisco.com/component/content/article/1/37.html



Re: subversion crash report

2011-03-16 Thread Lieven Govaerts
On Wed, Mar 16, 2011 at 11:08 PM, Ryan Schmidt
 wrote:
>
> On Mar 16, 2011, at 14:20, Darryl Fenwick wrote:
>
> > Apologies for the non-descriptive e-mail previously.  I was either updating 
> > or committing, I'm don't remember.  Sorry - not very helpful perhaps.

You were updating your trunk working copy, says so at the top of the log file:

Process info:
Cmd line: svn  up trunk

Is that trunk folder located directory under the root of a drive?

Based on the code in svn_dirent_is_child(), this might be related to:
http://subversion.tigris.org/issues/show_bug.cgi?id=3795

>
> > My subversion (version 1.6.15) on my 64-bit windows 7 machine has been 
> > unstable.  I get a lot of complaints about not being able to copy files 
> > from the tmp directory, etc, when I try to update.
> >

What type of complaints?

> > If you wish, I can continue to send you more information if ever I 
> > encounter problems.  Let me know.
> >
> > Darryl
>
> If you have further information to add, please do send it, but to the list, 
> not to me personally. I'm Cc'ing the list on this reply again.
>

Lieven


Re: subversion crash report

2011-03-16 Thread Ryan Schmidt

On Mar 16, 2011, at 14:20, Darryl Fenwick wrote:

> Apologies for the non-descriptive e-mail previously.  I was either updating 
> or committing, I'm don't remember.  Sorry - not very helpful perhaps.  
> 
> My subversion (version 1.6.15) on my 64-bit windows 7 machine has been 
> unstable.  I get a lot of complaints about not being able to copy files from 
> the tmp directory, etc, when I try to update.  
> 
> If you wish, I can continue to send you more information if ever I encounter 
> problems.  Let me know.
> 
> Darryl

If you have further information to add, please do send it, but to the list, not 
to me personally. I'm Cc'ing the list on this reply again.




Re: [svn] subversion crash report

2011-03-16 Thread Ryan Schmidt

On Mar 16, 2011, at 10:08, Darryl Fenwick wrote:

> Subversion crashed on my machine, and instructed me to send this crash log.  

What actions preceded that crash?




[svn] subversion crash report

2011-03-16 Thread Darryl Fenwick


Subversion crashed on my machine, and instructed me to send this crash log.


--
Darryl Fenwick
Streamsim Technologies, Inc
650 557 2196


Process info:
Cmd line: svn  up trunk
Version:  1.6.15 (r1038135), compiled Nov 24 2010, 15:10:31
Platform: Windows OS version 6.1 build 7600 

Exception: ACCESS_VIOLATION

Registers:
eax=02e493b8 ebx=0003 ecx= edx= esi=01fb2ea8 edi=
eip=002cb397 esp=0018f680 ebp= efl=00010246
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b

Stacktrace:
#1  0x002cb397 in svn_dirent_is_child ()


Loaded modules:
0x0040  C:\Program Files (x86)\CollabNet\Subversion Client\svn.exe 
(1.6.15.55095, 155648 bytes)
0x77d4  C:\Windows\SysWOW64\ntdll.dll (6.1.7600.16695, 1572864 bytes)
0x769b  C:\Windows\SysWOW64\kernel32.dll (6.1.7600.16385, 1048576 bytes)
0x75a8  C:\Windows\SysWOW64\KERNELBASE.dll (6.1.7600.16385, 286720 bytes)
0x6eec  C:\Program Files (x86)\CollabNet\Subversion Client\libapr-1.dll 
(1.4.2.0, 139264 bytes)
0x7780  C:\Windows\SysWOW64\advapi32.dll (6.1.7600.16385, 655360 bytes)
0x7591  C:\Windows\SysWOW64\msvcrt.dll (7.0.7600.16385, 704512 bytes)
0x759c  C:\Windows\SysWOW64\sechost.dll (6.1.7600.16385, 102400 bytes)
0x771c  C:\Windows\SysWOW64\rpcrt4.dll (6.1.7600.16385, 983040 bytes)
0x758b  C:\Windows\SysWOW64\sspicli.dll (6.1.7600.16484, 393216 bytes)
0x758a  C:\Windows\SysWOW64\CRYPTBASE.dll (6.1.7600.16385, 49152 bytes)
0x7790  C:\Windows\SysWOW64\ws2_32.dll (6.1.7600.16385, 217088 bytes)
0x76c5  C:\Windows\SysWOW64\nsi.dll (6.1.7600.16385, 24576 bytes)
0x7402  C:\Windows\System32\mswsock.dll (6.1.7600.16385, 245760 bytes)
0x772b  C:\Windows\SysWOW64\user32.dll (6.1.7600.16385, 1048576 bytes)
0x7692  C:\Windows\SysWOW64\gdi32.dll (6.1.7600.16385, 589824 bytes)
0x75a7  C:\Windows\SysWOW64\lpk.dll (6.1.7600.16385, 40960 bytes)
0x7672  C:\Windows\SysWOW64\usp10.dll (1.626.7600.16385, 643072 bytes)
0x75ad  C:\Windows\SysWOW64\shell32.dll (6.1.7600.16644, 12881920 bytes)
0x778a  C:\Windows\SysWOW64\shlwapi.dll (6.1.7600.16385, 356352 bytes)
0x1000  C:\Program Files (x86)\CollabNet\Subversion 
Client\libsvn_client-1.dll (1.6.15.55095, 204800 bytes)
0x6ee6  C:\Program Files (x86)\CollabNet\Subversion Client\libaprutil-1.dll 
(1.3.9.0, 192512 bytes)
0x6ee5  C:\Program Files (x86)\CollabNet\Subversion 
Client\libapriconv-1.dll (1.2.1.0, 36864 bytes)
0x002a  C:\Program Files (x86)\CollabNet\Subversion 
Client\libsvn_delta-1.dll (1.6.15.55095, 90112 bytes)
0x002c  C:\Program Files (x86)\CollabNet\Subversion 
Client\libsvn_subr-1.dll (1.6.15.55095, 716800 bytes)
0x74b2  C:\Windows\System32\shfolder.dll (6.1.7600.16385, 20480 bytes)
0x7762  C:\Windows\SysWOW64\ole32.dll (6.1.7600.16624, 1425408 bytes)
0x7750  C:\Windows\SysWOW64\crypt32.dll (6.1.7600.16385, 1163264 bytes)
0x7741  C:\Windows\SysWOW64\msasn1.dll (6.1.7600.16415, 49152 bytes)
0x0003  C:\Program Files (x86)\CollabNet\Subversion 
Client\libsvn_diff-1.dll (1.6.15.55095, 53248 bytes)
0x0037  C:\Program Files (x86)\CollabNet\Subversion Client\libsvn_ra-1.dll 
(1.6.15.55095, 520192 bytes)
0x0043  C:\Program Files (x86)\CollabNet\Subversion 
Client\libsvn_repos-1.dll (1.6.15.55095, 139264 bytes)
0x0046  C:\Program Files (x86)\CollabNet\Subversion Client\libsvn_fs-1.dll 
(1.6.15.55095, 135168 bytes)
0x005a  C:\Program Files (x86)\CollabNet\Subversion Client\libeay32.dll 
(1.0.0.2, 1286144 bytes)
0x006e  C:\Program Files (x86)\CollabNet\Subversion Client\ssleay32.dll 
(1.0.0.2, 245760 bytes)
0x74db  C:\Windows\System32\secur32.dll (6.1.7600.16484, 32768 bytes)
0x0072  C:\Program Files (x86)\CollabNet\Subversion Client\libsasl.dll 
(2.1.23.0, 77824 bytes)
0x0074  C:\Program Files (x86)\CollabNet\Subversion Client\libsvn_wc-1.dll 
(1.6.15.55095, 217088 bytes)
0x774a  C:\Windows\System32\imm32.dll (6.1.7600.16385, 393216 bytes)
0x767c  C:\Windows\SysWOW64\msctf.dll (6.1.7600.16385, 835584 bytes)
0x73e2  C:\Windows\System32\profapi.dll (6.1.7600.16385, 45056 bytes)
0x730e  C:\Windows\System32\uxtheme.dll (6.1.7600.16385, 524288 bytes)
0x72cc  C:\Windows\System32\security.dll (6.1.7600.16385, 12288 bytes)
0x6daf  C:\Windows\System32\credssp.dll (6.1.7600.16385, 32768 bytes)
0x6af8  C:\Windows\SysWOW64\msv1_0.dll (6.1.7600.16420, 270336 bytes)
0x6cc8  C:\Windows\System32\cryptdll.dll (6.1.7600.16385, 69632 bytes)
0x73ca  C:\Windows\System32\cryptsp.dll (6.1.7600.16385, 90112 bytes)
0x73c6  C:\Windows\System32\rsaenh.dll (6.1.7600.16385, 241664 bytes)
0x6a88  C:\Windows\System32\cryptui.dll (6.1.7600.16385, 1015808 bytes)
0x7406  C:\Windows\System32\nlaapi.dll (6.1.7600.16385, 65536 bytes)
0x73f1  C:\Windows\System32\dnsapi.dll (6.1.7600.16385, 278528 bytes)
0x73f0  C:\Windows\System32\winrnr.dll (6.1.7600.16385, 32768 bytes)
0x73ef  C:\Windows\System32\NapiNSP.dll (6.1.7600.16385, 65536 b

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, 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:
> http://svn.haxx.se/users/archive-2010-09/0065.shtml

The 1.6.13 binaries with a fix for this error should be on the site soon. (I
provided the binaries, but they have to be placed on the public site)

Bert
> hth,
> 
> Lieven



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:
http://svn.haxx.se/users/archive-2010-09/0065.shtml

hth,

Lieven