> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name] > > By hand!? I thought they had a rule in Programming School against > doing > repetitive tasks by hand like that. :-)
Believe me, I spent every minute of that time, imagining how complex my python script would be, and how to handle the exception cases... ;-) > 'gcc -pg' does this. And most likely there are other tools too. Thanks for that. Based on the man page, it might be more than I asked for. ;-) It says you need to add it during compile and linking, so ... I would add it to what, CFLAGS in the Makefile? CPPFLAGS? LDFLAGS? Reading the Makefile, it looks like COMPILE and LINK both take CFLAGS. So unless I'm wrong, I'll add "-pg" to the CFLAGS. Right? > > 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. We first experienced the problem in production. Clients connecting via svn:// to svnserver. Since I'm debugging, I'm able to reproduce it on the command line with svn, using svn:// so there is no server. I believe svn command line must be linking to the various server libraries you mentioned, but I need to know which one(s) to look into. The only way I know to do that is to start at the beginning. printf()'s inside of svn main() which tell me what process flow main() is following ... and finally ... it's spending its time in (some function) ... so I scatter printf()'s inside of (some function) and discover it's spending its time in (yet another function) so I go into it and scatter more printf()'s ... Again, thanks for the help.
