> From: "Alexander Mai" <[EMAIL PROTECTED]>
> To: "Jens-Peter Konrath" <[EMAIL PROTECTED]>
> CC: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>
> On Sat, 26 Aug 2000 14:41:36 +0200, Jens-Peter Konrath wrote:
>
> >Well,
> >I'd like to help out debugging mwm if I knew where to start.
> > I also have little to no knowledge about what a windowmanager
> > actally does...
> > Jens
Jens, I recommend OReilly's "Xlib Programming Manual". It
has a significant section on programming window managers, but
it is getting dated: it covers X11R4. However, everything
in it that I've encountered applies to X11R6, so it is a
good starting point, and changelogs, newer headers files,
etc., can be sources for grokking the delta.
I vaguely remember something about OReilly opening up
the X series... it may actually be available in .pdf or .ps
on their website. It has a companion volume "Xlib Reference
Manual", but having the Debian xbooks package, I feel less
need for that. "Programming", however, gives such a well
graded tutorial, that it is a "must have" for us beginners,
as is "X Toolkit Intrinsics Programming Manual", which also
has a companion "Reference", about which I also feel less
need, for the above reason.
> Well, even neglecting the kind of app (a WM) it is usually
> harder to debug an app which just ends up in a strange/locked
> state. I prefer the hard crashs ... ;-)
>
> One thing you could try is looking for a simple way to
> reproduce the problem. As an alternative one might also
> attempt a check for general problems, e.g. memory handling.
> I tried running mwm inside Xvfb when I got my crash
> yesterday (and an "unaligned access" on an alpha/DU system.
> Usually I only see those from my Fortran code ;-)
Other checkpoints might be swap usage, RAM size, source of
package -or, if you built it yourself, what warnings came
up in the compile-, X server & version.
