[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: another segfault during update

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 16 Apr 2009 15:20:48 -0400

C. Michael Pilato wrote:
> Stefan Küng wrote:
>> C. Michael Pilato wrote:
>>> Stefan Küng wrote:
>>>> Hi,
>>>>
>>>> In version 1.6.1, there's another possible segfault during updates:
>>>>
>>>> file libsvn_wc\update_editor.c, line 3522, function add_file():
>>>> if (!eb->switch_url
>>>> && strcmp(fb->new_URL, entry->url) != 0)
>>>>
>>>> The 'entry->url' is NULL according to crash dumps I got for TSVN.
>>> Looking at the code, I'd say this happens when update wants to add a new
>>> file in a working copy where a file of the same name is scheduled for
>>> addition. Does this match your reports?
>>>
>> I've only received an answer from one user about an hour ago, three
>> others haven't replied (yet?). But yes, this user mentioned that the
>> file was marked as added - at least he thought it was since he already
>> reverted his changes and retried the update (which then succeeded).
>> Sorry, wanted to report this, but I'm still going through my mail...
>>
>> If I get answers from the other users I tried to contact, I'll report
>> whatever info they could add.
>
> I think I found it (or another recipe?):
>
> In one working copy, commit the addition of a file "some/thing"
>
> In another working copy, do:
>
> svn mkdir some/thing
> rm -rf some/thing
> svn up
> *BOOM*

Tracking this in issue #3403
http://subversion.tigris.org/issues/show_bug.cgi?id=3403

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1753230

Received on 2009-04-16 21:21:05 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.