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

Re: xdelta, svndiff, zlib, or some other problem

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 2 Jul 2010 10:07:00 +0300 (IDT)

Edward Ned Harvey wrote on Thu, 1 Jul 2010 at 23:13 -0400:
> (This is where the question is.) I am asking you guys if there's any
> debug mode for svn, or any better way to debug.
>
> I went into subversion/svn, and I edited every single .c file. I put
> a fprintf(stderr,"function name\n"); into every function, just to show
> me where svn is going after it's initiated.

By hand!? I thought they had a rule in Programming School against doing
repetitive tasks by hand like that. :-)

'gcc -pg' does this. And most likely there are other tools too.

> There are a lot of files, and there are a lot of functions within
> those files. The flow of the program is far from straightforward.

You're looking in the wrong place. I'd focus on the server side, and
there --- on one of the libsvn_* libraries (e.g., fs, delta, or subr).
subversion/svn/ contains only the code specific to the command-line client
'svn'; you can safely ignore it unless you don't see the issue with other
clients.

>

There is a design diagram somewhere... (notes/*.html?) And if there
isn't, perhaps we should write up somewhere the libsvn_* interaction
DAG.
Received on 2010-07-02 09:08:12 CEST

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