OK, it turns out that resizing absolutely _any_ X application, then
moving the mouse outside the window will cause FVWM to core with the
same problem: Event.type is 64 and you get a core dump. I tried it with
Netscape, xterm, etc. and all did the same thing.
Note that if the memory after that array happens to be NULL, you won't
see anything go wrong; the event will just be ignored. So at least when
you're debugging FVWM, be sure to add a check for this or you might
think it doesn't happen on your system.
PS. Someone mentioned a way to create a "pseudo display" on your normal
display that you can use to start and debug another FVWM process; I
looked at ftp.x.org and found xpseudoroot-1.04 which looks
promising, but I can't get it to compile, even after toying with the
makefile and fixing a reference to dpy->display_name (changed to
DisplayString(dpy)), because it uses the functions LockMutex and
UnlockMutex which I can't find anywhere on my system.
I tried searching through the FVWM mailing list archives but
couldn't find anything about it.
Is there a newer version of xpseudoroot or another app that does the
same thing?
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
Senior Software Engineer Bay Networks, Inc.
-----------------------------------------------==<
http://www.baynetworks.com/>-
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions--Bay Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Wed Mar 13 1996 - 12:38:25 GMT