On Tue, 2009-02-24 at 12:03 +0530, Jaydeep Ghurye wrote: > Apparently, the log file is not providing any additional information > than what we already have. Kindly let me know if there is anything > else that we can do to get to the root of this problem.
Can you also raise the debugging to DEBUG (instead of just WARN). There
should be a lot more debugging information before this message.
> Can you tell me if there is any tool available that can help me debug
> SCMBUG at run-time? I mean an editor with debugging facilities, like
> you have in Turbo C++ or Visual Basic, where you have features for
> adding breakpoints, adding a 'Watch' to variables and monitoring the
> flow of the program using step mode etc.
I don't know of such tools. But the calls to Scmbug originate from
<repository>/hooks/{pre,post}-commit. That's where you could intercept
them. Beware that Subversion cleans up any environment variables before
calling these.
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
