1FvwmGtkDebug(1) Fvwm Modules FvwmGtkDebug(1)
2
3
4
6 FvwmGtkDebug - graphical interactive fvwm module debugger
7
9 FvwmGtkDebug should be spawned by fvwm(1).
10
11 To run this module, place this command somewhere in the configuration:
12
13 Module FvwmGtkDebug
14
15 To stop this module, just close the GUI window, the usual KillModule
16 works too.
17
18 You may also run this application as a regular program from the command
19 line shell. But the communication with fvwm is not established in this
20 dummy mode, so commands are not really sent and there are no real
21 events received. However certain activity is emulated using dummy
22 events.
23
25 This module monitors all fvwm event information and shows it nicely in
26 the interactive gtk+ application. Good for debugging and educational
27 purposes.
28
29 Among the features: command console with history and auto command help,
30 requesting to send back ConfigInfo (configuration of fvwm and all
31 modules), WindowList (information about all windows) or custom Reply.
32
33 The fvwm commands may be executed within the context of some window.
34 The context window may be optionally set on invocation, like: "Next
35 (Navigator) FvwmGtkDebug", and be set/unset interactively at any time.
36
38 There are several command line switches:
39
40 FvwmGtkDebug [ --mask mask ] [ --xmask mask ] [ --debug level ]
41
42 Long switches may be abbreviated to shorter switches.
43
44 -m|--mask mask - set the initial module mask, 31 bit integer. This mask
45 may be changed interactively at any time. By default almost all events
46 are monitored (except for some flood events like CONFIGURE_WINDOW or
47 FOCUS_WINDOW. The special value of -1 sets the maximal mask.
48
49 -x|--xmask mask - set the initial module extended mask, 31 bit integer.
50 This mask may be changed interactively at any time. By default almost
51 all events are monitored (except for some flood events like
52 ENTER_WINDOW or LEAVE_WINDOW. The special value of -1 sets the maximal
53 extended mask.
54
55 -d|--debug level - use the Perl library debugging mechanism. The useful
56 levels are 2 to 4.
57
59 See also FvwmDebug, "fvwm-perllib man events".
60
62 Mikhael Goikhman <migo@homemail.com>.
63
64
65
662.5.28 (from cvs) 2009-03-22 FvwmGtkDebug(1)