1FvwmDebug(1)                     Fvwm Modules                     FvwmDebug(1)
2
3
4

NAME

6       FvwmDebug - the fvwm module debugger
7

SYNOPSIS

9       FvwmDebug should be spawned by fvwm(1) for normal functionality.
10
11       To run this module, place this command somewhere in the configuration:
12
13           Module FvwmDebug [optional-params]
14
15       To stop this module, execute:
16
17           KillModule FvwmDebug
18

DESCRIPTION

20       This module persistently dumps all fvwm event details and optionally
21       some other information into the standard error stream or a file, good
22       for debugging purposes. The output may be optionally redirected to
23       xconsole or similar window.
24

INVOCATION

26       There are several command line switches:
27
28       FvwmDebug [ --args|--noargs ] [ --events|--noevents ] [ --log file ] [
29       --xconsole ] [ --mask mask ] [ --xmask mask ] [ --debug level ] [
30       --track tracker-name ] [ --send-configinfo ] [ --send-windowlist ]
31
32       Long switches may be abbreviated to shorter switches.
33
34       --noargs - do not print all arguments of the event, just its name.
35       --args is the default.
36
37       --noevents - do not print even event names, implies --noargs. It is
38       similar in effect to setting both --mask and --xmask to 0, but the
39       events are actually received by the module, they are just not printed.
40
41       This option may be useful if --track or/and --debug is used.
42
43       The default is --events normally, and --noevents if one or more --track
44       options specified.
45
46       -l|--log file - specify the log file name instead of the standard error
47       stream. If the log file can't be open for writting, the default
48       standard error stream is used.
49
50       The file may start with a pipe '|', this is similar to the usual
51       meaning of a pipe, the output is piped to the specified command. See
52       also --xconsole option.
53
54       -xc|--xconsole - this is a shortcut for:
55
56           FvwmDebug --log '|xconsole -file /dev/stdin -geometry 600x400 -notify'
57
58       That shows the module output in the xconsole window rather than the
59       standard error stream.
60
61       -m|--mask mask - set the module mask, 31 bit integer. By default almost
62       all events are monitored (except for some flood events like
63       CONFIGURE_WINDOW or FOCUS_WINDOW. The special value of -1 sets the
64       maximal mask.
65
66       -x|--xmask mask - set the module extended mask, 31 bit integer. By
67       default almost all events are monitored (except for some flood events
68       like ENTER_WINDOW or LEAVE_WINDOW. The special value of -1 sets the
69       maximal extended mask.
70
71       -d|--debug level - use the Perl library debugging mechanism. The useful
72       levels are 2 to 4.
73
74       -t|--track tracker-name - create the given Perl library tracker and
75       observe its main observable. This option may be specified multiple
76       times. This options implies --noevents unless explicitely overwritten.
77       You may optionally try --debug, for example:
78
79           FvwmDebug -xc --track PageInfo --track GlobalConfig --debug 3
80
81       Run "fvwm-perllib man" to get the names of all existing trackers in
82       your installed Perl library.
83
84       -sc|--send-configinfo - send Send_ConfigInfo command to fvwm on
85       startup, this results in a lot of events received.
86
87       -sw|--send-windowlist - send Send_WindowList command to fvwm on
88       startup, this results in a lot of events received.
89

SEE ALSO

91       See also FvwmGtkDebug.
92

AUTHOR

94       Mikhael Goikhman <migo@homemail.com>.
95
96
97
982.5.28 (from cvs)                 2009-03-22                      FvwmDebug(1)