On 16.10.2009 10:31, Jon Nicoll wrote:
> Hi all
> I'm using TortoiseHg 0.8.3 on an XP machine which I use for program
> development. I use the windows utility DebugView to view debug output
> sent by my program to the windows debug mechanism via
> OutputDebugString and its variants.
>
> Unfortunately I'm seeing that TortoiseHg also outputs a lot of of debug
> information using the same mechanism. This kind of thing:
>
> [3256] [THG] DllGetClassObject clsname = CLSID_TortoiseHg2
> [3256] [THG] CShellExt::GetOverlayInfo: myTortoiseClass = M
> [3256] [THG] DllGetClassObject clsid = {B456DBA1-7BF4-478C-937A-05130C2C212E}
> [3256] [THG] DllGetClassObject clsname = CLSID_TortoiseHg1
> [3256] [THG] CShellExt::GetOverlayInfo: myTortoiseClass = A
> [3256] [THG] DllGetClassObject clsid = {B456DBA6-7BF4-478C-937A-05130C2C212E}
> [3256] [THG] DllGetClassObject clsname = CLSID_TortoiseHg6
> [3256] [THG] CShellExt::GetOverlayInfo: myTortoiseClass = ?
> [2832] [THG] [C] findHgRoot(E:\ASL0658\.svn): NO repo found
> [2832] [THG] [C] hasHgDir: PathIsDirectory("E:\0658\service_test\.hg") ->
> 0, in 16 ticks
> [2832] [THG] [C] findHgRoot(D:\Documents and Settings\jnicoll\UserData):
> NO repo found
> [2832] [THG] [C] findHgRoot(D:\Documents and Settings\LocalService): NO
> repo found
> [2832] [THG] [C] findHgRoot(D:\Program Files): NO repo found
> [2832] [THG] [C] findHgRoot(E:\0658): NO repo found
> [2832] [THG] [C] findHgRoot(E:\ASL0658\Changes): NO repo found
> [2832] [THG] [C] findHgRoot(E:\09289963ec639b503392): NO repo found
> [2832] [THG] [C] findHgRoot(E:\0658\.svn): NO repo found
>
> etc. (The [2832]process ID is added by DebugView in this case; the [THG]
> is TortoiseHG's own, I think)
>
> This is a perfectly reasonable thing to have during development. But could
> it be removed in releases please? It gets in the way of other things...
>
> (alternatively, if there's some mechanism to prevent such output in a
> release build I would like to know of it - thanks)
>
I would like to keep it enabled by default. Actually we ship the
debug build of the shell extension in releases (the release build
of the shell extension actually cannot emit any debug output at
all).
This debug output helped immensely in the past to diagnose shell
extension or context menu problems reported by users.
After all, TortoiseHg hasn't yet reached 1.0 in revision numbers :)
But I understand your point. Maybe we could introduce some
hidden registry setting to turn these debug outs off.
In the mean time, you could use the filter feature of DebugView:
Choose "Filter/Highlight..." from the "Edit" menu of DebugView
and enter "[THG]" in the "Exclude" field.
This will exclude all debug lines beginning with "[THG]".
All debug output of the shell extension begins with "[THG]".
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
