2009/6/30 Manoj Srivastava <[email protected]>: > Hi, > > This was reported by a Debian use. Please retain the CC to > [email protected] so that the Dewbian BTS has a > copy of your contribution. > > I have not been able to reproduce this crash, but I am passing > it along in case someone here has a better view into this. > > Originally reported for version 2.5.21; and most recently > reconfirmed for version: 2.5.23 and 2.5.25. > > > --8<---------------cut here---------------start------------->8--- > EvwmEvent segfaults every time. I get this in my dmesg: > > FvwmEvent[3014]: segfault at 0000000000000000 rip 00002af1873cfcdc rsp > 00007fff240ad048 error 4 > > I found out that if the following line exists in my config-file, > FvwmEvent seg-faults at startup: > > *FvwmEvent: toggle_paging metal.au > > Also, after trying several modifications to the config-file, both > FvwmEvent and fvwm seg-faults very easily. The config-file parser > seems to be broken, at least on amd64.
I've committed a fix for this to CVS. The introduction of a new module message in 2.5.19 made the event table off by one for the trailing events (breaking startup, shutdown and unknown), and if a config name didn't match a known event would cause deference of a uninitialized static array element. (gcc sets them to null) The patch is one line, but is just as unrouboust as before, and will break again with the introduction of new Module messages. A proper patch would change the handling of the module messages to skip messages not dealt with in the module. /Viktor
