Kiln » TortoiseHg » TortoiseHg
Clone URL:  
Pushed to one repository · View In Graph Contained in 0.8.2, 0.8.3, and 0.9

stable doc: fill in debugging info

Changeset 673af427b2b4…

Parent 09ee8e98c448…

by Steve Borho

Changes to one file · Browse files at 673af427b2b4 Showing diff from parent 09ee8e98c448 Diff from another changeset...

Change 1 of 1 Show Entire File doc/​source/​debugging.txt Stacked
 
4
5
6
7
8
 
 
9
10
 
 
 
 
 
 
 
 
 
 
 
11
12
13
14
15
 
 
 
 
 
16
17
18
19
20
 
 
 
 
 
 
21
22
23
24
25
26
 
27
28
29
30
31
 
 
 
 
 
 
 
 
 
 
32
33
34
35
36
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
4
5
6
 
 
7
8
9
 
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
 
25
26
27
28
29
30
31
32
33
 
34
35
36
37
38
39
40
41
42
43
44
 
45
46
47
48
49
 
50
51
52
53
54
55
56
57
58
59
60
61
62
63
 
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
@@ -4,33 +4,84 @@
 .. module:: debugging   :synopsis: Debug problems in shell extension or dialogs   -Debugging hgtk --------------- +Debugging Dialogs +-----------------   -TODO +Stderr is being captured to a buffer that is being inspected at program +exit. If any serious errors (tracebacks, etc) are found in the stderr +buffer the entire contents are sent to the bug report tool so the user +can (should) report a bug. If you suspect there are errors that are not +being reported, you can set the environment variable **THGDEBUG** to any +value to disable the stderr buffering. + +If you have a bit of Python knowledge, you can also use:: + + hgtk --debugger <command> +    Windows  ~~~~~~~   -TODO +To debug the changelog viewer, for instance, enter these commands +into a :command:`cmd.exe` window, while inside the repository:: + + set THGDEBUG=1 + hgtk log    Linux/MacOSX  ~~~~~~~~~~~~   -TODO +To debug the changelog viewer, for instance, enter these commands +into your shell window, while inside the repository:: + + export THGDEBUG=1 + hgtk log +      Debugging Shell Extension  -------------------------   -TODO +The debugging mechanisms depend on your platform.    Windows  ~~~~~~~   -TODO +See also http://msdn.microsoft.com/en-us/library/cc144064(VS.85).aspx +for some info bits about Running and Testing Shell Extensions on Windows + +The :command:`DbgView` tool from the SysInternals suite will capture +debug messages from the shell extension. + +The :command:`ThgTaskbar` application's options dialog has an error +logging tab. If you have this dialog open while you are browsing +folders, you will get info and error level messages from the icon +overlay refresh process.    Nautilus  ~~~~~~~~   -TODO +Debugging is done via the environment variable DEBUG_THG + +* to test in a separate process:: + + DEBUG_THG=Ne TMPDIR=/tmp/anydir/ --no-desktop nautilus [path] + +* to test in the main instance:: + + nautilus -q + DEBUG_THG=NOe nautilus + +* permanent debugging, set DEBUG_THG in a file which is read on session + start (~/.profile, ~/.xprofile) + +Upper case characters in DEBUG_THG specify modules. Only *O* and *N* +for *OverlayCache* and *Nautilus*, respecively, are supported module +names. Lower case characters imply parts. Only *e* is supported, +implying *error* messages. + +To restart nautilus, chose either + +1) killall nautilus (the session restarts nautilus automatically, stdin and stdout go to ~/.xsession-errors) + +2) nautilus -q; nautilus (stdin and stdout are on the console)