----- Original Message -----
From: Damon Rand firstname.lastname@example.org
Sent: Sunday, January 26, 2003 3:22 PM
Subject: Re: [Issue 5] - Crash when using compare with working copy from
------- Additional Comments From email@example.com 2003-01-26 03:53
Can't reproduce that. Works for me.
What system are you using? Does it crash both for http and local
If it only crashes for local reps then the bug is already solved
(inconsistency of the c-runtime 'cause we used the berkeley build with
VC6 instead of VS.NET).
I'm using 17.1 client against 17.0 repos..
Win2k/Sp3. Everything is default install.
I was not using the new VC.NET compiled db4-win32 libraries. I have tried
these libraries now but am still getting the same error..
what kind of error do you exactly get? If the TortoiseProc.exe part crashes
should pop up a crashhandler which you can use to send me an email with the
stacktrace and the crashdump file. If it's just a dialog box popping up with
error description then please give me that message.
Could there be some version difficulties because you compiled against 4559
and I am running 4503?
There shouldn't be, but I can't be sure of that...
Also 'Show logs' needs an abort button. I did 'Show logs' on svn-head and
took quite some time. ;-)
See issue #1004 which gets solved in the next subversion release.
I had a different approach for that but it didn't work well:
- fetch the last 20 entries
- give a button to get 20 more
the problem was that for most files (not the parent dir) there were NO
log entries for more than 20 revisions - so when the button was pressed
no additional entries appeared. Then I tried to automatically fetch log
messages until 20 got delivered but that resulted in sometimes 10 or more
established and closed connections.
So now I just wait for issue #1004 to get into the subversion source...
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Oct 14 02:18:08 2006