I got, and confirmed, a report from a Debian user that starting gnubg in the ru_RU.KOI8-R locale causes a segfault after clicking on New Game. This doesn't seem to affect other locales (I tried German). It seems suspiciously like a memory clobber. The backtrace isn't particularly useful:
(gdb) bt #0 0xb7ee1335 in ?? () from /usr/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-xpm.so #1 0x00000000 in ?? () I'm happy to help with further debugging, but am not sure the best way to go about doing so. valgrind reports an access to memory that isn't on the stack or malloc'd (after bumping the valgrind error limit -- gnubg produces a *ton* of valgrind errors, many of which in its dependent libraries) deep inside the XPM loader, and I couldn't see anything obviously wrong with the call site. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
