if you will look at the top of your pre-commit.bat (or pre-commit.tmpl) file, 
you will see an explanation about %REPOS% and %TXN%. in short, these are 
parameters passed to the pre-commit hook by SVN. %REPOS% is the path to your 
repository, and %TXN% is a transaction ID of the current commit. of course, 
once the commit is finished, this id doesn't represent anything anymore, so you 
can't use it outside the context of a commit.
there could be a way to interact with the pre-commit hook, i'm not sure. maybe 
if you will run subversion in a console and not as a service. if you know C, 
perhaps you could write a little program that will act as the pre-commit hook 
(you will have to call it pre-commit.exe), run the scmbug script in debug mode 
with the CreateProcess Win32 API function, capture it's output to print it to 
screen and send your input to the debugger. it's a long shot, but it might 
work. It will be easier to write it in C#, come to think of it, with the 
Process.Create() method.

tsahi.


 --
The day Micro$oft sells something that doesn't SUCK
is the day they start selling vacuum cleaners.
http://www.geocities.com/tsahi_75




________________________________
From: Jaydeep Ghurye <[email protected]>
To: Tsahi Asher <[email protected]>; [email protected]
Sent: Wednesday, February 25, 2009 4:11:06 PM
Subject: Re: [scmbug-users] Problem with Commit using Subversion and Bugzilla.




On Wed, Feb 25, 2009 at 7:28 PM, Jaydeep Ghurye <[email protected]> 
wrote:

Hi Tsahi,
             Thanks for the input. I haven't yet tried this option, but I do 
have a query. The file pre-commit.bat runs the command
 
"C:/Perl/bin/perl" -I %REPOS%/hooks/lib/scmbug 
%REPOS%/hooks/bin/scmbug_activity.pl %REPOS%/hooks/etc/scmbug/glue.conf 
activity_verify %REPOS% %TXN% >&2
 
I could use the -d option on this, but I am not sure what %REPOS% or %TXN% 
stand for, or where they are derived from. It's logical that %REPOS% refers to 
the repository and I can probably replace it with the path to the same, but I'm 
not sure what I can use in place of %TXN%. Does Subversion store old 
transaction IDs somewhere? I looked under the %REPOS%/db/transactions folder 
and didnt find any. I would like to use a valid transaction ID in place of this 
%TXN% to try and debug the problem.
 
Thanks,
Jaydeep.


On Wed, Feb 25, 2009 at 1:01 AM, Tsahi Asher <[email protected]> wrote:


you can run perl.exe with the -d parameter in a console window, such as

>perl -d <script name>

which will allow you all of these, although in text mode and not a graphic IDE.

tsahi

 --
The day Micro$oft sells something that doesn't SUCK
is the day they start selling vacuum cleaners.
http://www.geocities.com/tsahi_75




----- Original Message ----
> From: Kristis Makris <[email protected]>
> To: Jaydeep Ghurye <[email protected]>
> Cc: [email protected]
> Sent: Tuesday, February 24, 2009 6:33:24 PM
> Subject: Re: [scmbug-users] Problem with Commit using Subversion and Bugzilla.
>
> 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

> /hooks/{pre,post}-commit. That's where you could intercept
> them. Beware that Subversion cleans up any environment variables before
> calling these.


      
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to