>> Charles Hines(C) wrote on Tue, 03 Oct 1995 13:38:55 -0400:
C> Would everyone that is seeing odd problems like this please run fvwm2
C> with the -debug parameter and see if the problems continue.
No, the problem disappears. But, man, does it sloooowww fvwm down ;-).
I couldn't get it to fail after four restarts, but the fifth restart
*did* fail. Ugh. Doesn't look like a fun one to find.
C> All this does is run XSynchronize(dpy,1);, which may cause problems
C> to more clearly show up, or go away, or might not show anything.
C> I'm merely curious.
This is what I fond in my logfile -- the first one is my fault for
(foolishly) putting a "Restart fvwm -debug" in my menu w/o checking
the manual.
FVWM: Call of 'fvwm -debug' failed!!!!
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 66 (X_PolySegment)
Resource id in failed request: 0x4000001
Serial number of failed request: 39
Current serial number in output stream: 45
C> Another possibility - what level of optimization is everyone compiling
C> with? -O3 and greater sometimes causes strange problems with
C> programs, so I'd say keep it at -O2 or just -O.
I've only tried to use -O.
-mb-
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Oct 03 1995 - 14:31:02 BST