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

Re: SEGFAULT in 'svn pget' (no time to diagnose)

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2007-11-05 15:42:11 CET

C. Michael Pilato wrote:
> Blair Zajac wrote:
>> Is it safe to do that, given that paths are run through these steps?
>> Are there any UTF-8 issues I need to be aware of, in the following
>> Python pseudo code?
>> (peg_rev, path) = svn_opt_parse_path(path)
>> path = svn_path_cstring_from_utf8(path)
>> path = apr_filepath_merge(path)
>> path = svn_path_cstring_to_utf8(path)
>> path = svn_path_canonicalize(path)
>> path = "%s@%s" % (path, peg_rev)
> Well, that last step would of course not re-add a peg-rev if there wasn't
> one to begin with, but other than that, I don't know of any issues with this
> path handling plan. Where in all this does conversion to internal style
> occur? Inside svn_opt_parse_path()?

By the way, I've filed issue #3012 to track this.

C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Mon Nov 5 15:44:24 2007

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.