Todd C. Gleason wrote:
>> I don't use WinDbg that often. But I guess that the abort() call works
>> against this goal since it aborts the whole process.
>>
>> Can you maybe try a nightly build? Maybe the crash is already fixed.
> But
>> if not: in 1.6, Subversion finally got rid of abort() and exit() calls
>> and replaced them with a custom exception handler. TSVN in this case
>> shows an error dialog with the source code location where the problem
>> originated and any info it gets from that exception. Which would make
>> this a little bit more suitable to find the problem.
>
> I haven't yet tried a large merge, but I had quite a few other
> TortoiseProc crashes. Often it would happen during an svn update as
> well, so then I'd just go to the cmd line and do a cleanup and update,
> and that would work. In any case, after quite a bit of frustration with
> the crashes I installed
>
> TortoiseSVN-1.5.99.15563-dev-win32-svn-1.6.0-dev.msi
>
> And so far I haven't had any more crashes with updates, commits, or
> small merges. I guess this probably means that the svn libs have fixed
> something, but as to why the 1.5.5 command line doesn't misbehave at all
> for me, I have no idea.
Don't forget that TSVN usually passes --non-recursive for updates, and
some other params for merges which you might not have passed when trying
with the CL client.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1278753
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-06 21:10:02 CET