Gleb Smirnoff <gleb...@glebius.int.ru> writes: > Hi! > > Just got a very different panic. It may be unrelated > to the free/malloc problems, but since fvwm was rock stable > for the last 10 years for me, I'm prone to think that all > my recent crashes are caused by the same single problem. > > (gdb) bt > #0 0x00000000004daab8 in FlocaleDrawString (dpy=0x804831000, > flf=0x80482f980, > fws=0x80482aec0, flags=0) at Flocale.c:1983 ... > Core saved, I can provide more info.
Starting to look like a memory overlay somewhere. In which case valgrind or one of the other memory checkers would be more useful. Do "list". Print fws, *fws, comb_chars, i. -- Dan Espen
