Re: multiple crashes

On Fri, May 25, 2012 at 3:43 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 25.05.2012 10:54, Philip Martin wrote:
>>
>> Stefan Küng<tortoisesvn_at_gmail.com>  writes:
>>
>>> libsvn_tsvn32!svn_relpath_join+0x10
>>> libsvn_tsvn32!svn_wc__internal_get_origin+0x1b2
>>> libsvn_tsvn32!svn_client_commit5+0x14d3
>>> libsvn_tsvn32!svn_client__harvest_committables+0x26a
>>> libsvn_tsvn32!svn_client_commit5+0x2e4
>>>
>>> here the 'status' after svn_wc__db_scan_addition() is
>>> svn_wc__db_status_incomplete which might be an indication why
>>> original_repos_relpath is NULL and then causes the access violation in
>>> svn_relpath_join().
>>
>>
>> One way to get incomplete with status add is to interrupt a wc-to-wc
>> copy.  That gives things like:
>>
>> $ svn st wc
>> A  +    wc/X
>> !       wc/X/B
>> !       wc/X/f
>>
>> But those have original_repos_relpath and the commit doesn't crash.
>>
>> Is there some other way of getting incomplete with add?  Perhaps an
>> interrupted merge?
>
>
> No idea how the wc got into this state. As I said: this comes from a crash
> dump. All I can see is the stack trace and some of the variables passed to
> the functions in the stack trace.

count is now up to 46 dumps for this exact crash.
It's now the top crash which hasn't been resolved yet.

Going through the others now, be back soon with other crashes which
happen in the svn library.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net