Re: [Lxr-dev] genxref and warnings from cvs co (was: /bin/true as a zombie)

[<pe...@kl...>]

Kevin Way <kev...@ov...> writes:

> Any chance you've made progress on the DB connection bug?

Not really, but I have made some progress on the co thing instead,
which was at least for me several different bugs.

1) Somehow the %cvs hash wasn't cleared when new files were being
   parsed.  The result was that we'd try to check out non-existant
   versions.  One-line fix, I think I already committed that one.  I
   do _so_ hate global variables.

2) Some of my CVS files contained symbols pointing to non-existant
   versions.  Since LXR always translates symbols to versions before
   checking out, that also resulted in trying to check out
   non-existant versions, and also resulted in the branching errors.
   The fix I have is that I run a consistency check on the symbols,
   deleting the ones that have no corresponding version.
   Unfortunately that seems to make genxref even slower.  Noticeably
   slow.  Alternatively that may have been a problem with our server,
   which had problems with one of its CPUs, its swap and at least some
   of its raid disks yesterday.  

   I'd like some feedback on wether this seems like an acceptable fix,
   or wether we'd rather just live with co failing from time to time.

3) I had some errors where co complained about premature end of file
   or someting.  These were on binary files (jpegs), and it's entirely
   possible that the files are corrupt.  I have ignored these for now.


...Peder...
-- 
Cogito ergo panta rei.