One thing I noticed is that in both the small and large log message cases we don't get the following reported in the logfile:
SCM.pm: prepare_activity - return I don't get it Mike. I sincerely don't understand where the problem is. It's as if the process suddenly stops. Have you been trying all this through Apache ? Is it possible to try committing with a large log message when Apache is not part of the equation ? On Thu, 2008-01-17 at 14:39 -0600, Brown, Mike wrote: > Kristis, > > The additional logging doesn't show anything in the failed case. I've > attached the SCM.pm file with the logging I added and the log file for the > good and base cases. Let me know what to try next. > > Regards, > Mike > > -----Original Message----- > From: Kristis Makris [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 17, 2008 2:12 PM > To: Brown, Mike > Cc: '[email protected]' > Subject: RE: [scmbug-users] very large commit comments break scmbug + > bugz illa > > > The last place that remains to be debugged is > SCM.pm.in:prepare_final_log_message. It's seems heavy in terms of > processing, but still should return quickly with a small log file. > > And perhaps debugging statements in SCM.pm.in:prepare_activity. But > prepare_final_log_message seems like the root of the problem. Perhaps we > are not parsing with regexs something right and lead to an infinite loop > somehow ? > > On Thu, 2008-01-17 at 13:55 -0600, Brown, Mike wrote: > > Kristis, > > > > Attached is the logfile from a "good" small log message commit and a "bad" > > big log message commit using your patch to the Connection.pm file. > > > > Nothing was logged by Connection.pm in the failed case. > > > > Regards, > > Mike > > > > -----Original Message----- > > From: Kristis Makris [mailto:[EMAIL PROTECTED] > > Sent: Thursday, January 17, 2008 1:40 PM > > To: Brown, Mike > > Cc: '[email protected]' > > Subject: RE: [scmbug-users] very large commit comments break scmbug + > > bugz illa > > > > > > On Thu, 2008-01-17 at 12:58 -0600, Brown, Mike wrote: > > > Krisitis, > > > > > > I found that the logfile was not being written because of a permissions > > > conflict. I fixed the permissions issue and also put in the logging you > > > suggested with some additional log messages. I've attached 5 files for > > your > > > review: > > > > > > a) Subversion.pm with logging > > > b) Glue.pm with logging > > > c) logfile generated with a small commit message (this worked) > > > d) logfile generated with the large commit message (this failed) > > > e) text file containing large commit message > > > > I'm glad it was just a permissions issue. The debugging information you > > provided is great. > > > > I'm wondering if the freeze has something to do with the socket opened > > to the daemon. Can you add the following debugging patch too ? > > > > http://bugzilla.mkgnu.net/show_bug.cgi?id=1093#c12 > > > > We need to add officially add logging in the glue, really. > > > > >
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
