And as I've said in the fvwm-workers mailing-list:
Concerning the bug 1393 (corresponding to bug 263945 in Debian),
it seems to be due to a wrong skip value for the buttons. Consider
the following part of the modules/FvwmWinList/ButtonArray.c code:
Button *ButtonNew(char *title, FvwmPicture *p, int up)
{
Button *new;
new = (Button *)safemalloc(sizeof(Button));
The memory pointed by new contains random data, so that one can
normally add the following line:
new->skip = 1;
without changing the behavior. With this added line, the bug is much
more reproducible. I don't know what is the fix (forcing new->skip to
0 here makes the bug normally appear, probably because some buttons
must be skipped).
--
Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
