Derek Price wrote: > Actually moving the code would be complicated and not symetrical. I > dislike having a process responsible for disposing of temporary data it > did not create. > > In the CVS client/server architecture, there are two servers. The first > authenticates the client and interprets the data coming across in such a > manner as to construct a duplicate of the client workspace. It then > launches a second server which runs, (mostly) unaware that it is not a > CVS application running in local mode against a local repository. > Meanwhile the first server acts in the background, translating the > second server's output into something acceptable to the client. When > the second server completes its job, it exits, then the first server > cleans up the temp space. > > It is this second server's core dumps that are being caught. It > wouldn't be impossible to make it responsible for cleaning up its own > workspace (which it did not create), but it would be a lot of work. > Right now, there is a simple switch in the first server which detects > when the child dumps core and skips the workspace cleanup with an > informative error message.
Thanks for explaining. Your objective is clear now. But how would you want this to work on Woe32? I assume that you would want this debugging feature also on Windows. How do you implement it there? > The change I'm proposing is simple. I've attached a patch. I'm opposed to this change because I don't see how it can be made to work on Windows. In other words, it makes unportable assumptions. Bruno _______________________________________________ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
