This looks like a gnubg compiled without -g. You should compile with -g and at most -O2, -O1 is better.
Christian > Program received signal SIGILL, Illegal instruction. > [Switching to thread 3764.0xa24] > 0x05281278 in ?? () > (gdb) thread apply all bt > > Thread 2 (thread 3764.0xa24): > #0 0x05281278 in ?? () > #1 0x0d94f1e8 in ?? () > #2 0x003d0000 in ?? () > #3 0x00000000 in ?? () > > Thread 1 (thread 3764.0xcac): > #0 0x617a5690 in gtk_button_get_type () from > D:\Documents\gnubg\libgtk-win32-2.0-0.dll > #1 0x617a9d97 in gtk_button_state_changed () from > D:\Documents\gnubg\libgtk-win32-2.0-0.dll > #2 0x63a43955 in g_closure_invoke () from > D:\Documents\gnubg\libgobject-2.0-0.dll > #3 0x63a57892 in signal_emit_unlocked_R () from > D:\Documents\gnubg\libgobject-2.0-0.dll > #4 0x00000000 in ?? () > #0 0x05281278 in ?? () > > > > Christian Anthon <[email protected]> wrote on 24/06/2009 15:36:19: > >> Try this instead: >> >> thread apply all bt >> >> Christian. >> >> On Wed, Jun 24, 2009 at 3:28 PM, Massimiliano >> Maini<[email protected]> wrote: >> > >> > Christian Anthon <[email protected]> wrote on 24/06/2009 >> > 12:53:50: >> > >> >> > >> >> > Is there anything I can do to track this down ? I have a non-stripped >> >> > exe, >> >> > ig yuo give me detailed instruction on how to run it with gdb I can >> >> > send >> >> > you >> >> > the output (if any, since I have to manually kill when it freezes). >> >> > >> >> >> >> Assuming that you have gdb installed in your path: >> >> >> >> make a copy of the gnubg.bat file and just insert gdb before gnubg.exe >> >> on the same line. Run ->Crash -> type bt in the gdb prompt >> > >> > Here it is: >> > >> > D:\Documents\gnubg>gdb gnubg-gui-py-sse-gmt.exe-debug.exe >> > GNU gdb 6.8 >> > Copyright (C) 2008 Free Software Foundation, Inc. >> > License GPLv3+: GNU GPL version 3 or later >> > <http://gnu.org/licenses/gpl.html> >> > This is free software: you are free to change and redistribute it. >> > There is NO WARRANTY, to the extent permitted by law. Type "show >> > copying" >> > and "show warranty" for details. >> > This GDB was configured as "i686-pc-mingw32"... >> > (gdb) run >> > Starting program: D:\Documents\gnubg/gnubg-gui-py-sse-gmt.exe-debug.exe >> > [New thread 1392.0xfd0] >> > GNU Backgammon 0.90-mingw 20090624-gcc44 >> > Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 by Gary Wong. >> > Copyright (C) 2009 by Gary Wong and the AUTHORS; for details type `show >> > version'. >> > This program comes with ABSOLUTELY NO WARRANTY; for details type `show >> > warranty'. >> > This is free software, and you are welcome to redistribute it under >> > certain >> > conditions; type `show copying' for details. >> > [New thread 1392.0xd94] >> > >> > Program received signal SIGSEGV, Segmentation fault. >> > [Switching to thread 1392.0xd94] >> > 0x05281278 in ?? () >> > >> > (gdb) bt >> > #0 0x05281278 in ?? () >> > #1 0x0d8dc098 in ?? () >> > #2 0x003d0000 in ?? () >> > #3 0x00000000 in ?? () >> > (gdb) >> > >> > Guess you were expecting someting more than this ... >> > >> > MaX. >> > > _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
