Hi there, Gonéri Le Bouder [EMAIL PROTECTED] wrote:
> In the Debian Games Team, we were not able to reproduct the bug. Can you > please provide a full gdb backtrace. > http://wiki.debian.org/HowToGetABacktrace Sure, but unfortunately the result is this: (gdb) set pagination 0 (gdb) run Starting program: /usr/games/xmoto [Thread debugging using libthread_db enabled] [New Thread 0xb716f6d0 (LWP 20447)] [New Thread 0xb716eb90 (LWP 20450)] [New Thread 0xb35beb90 (LWP 20451)] [New Thread 0xb2dbdb90 (LWP 20452)] [Thread 0xb2dbdb90 (LWP 20452) exited] [New Thread 0xb25bcb90 (LWP 20453)] [Thread 0xb25bcb90 (LWP 20453) exited] ----- And here xmoto just freezes, instead of the expected crash. So, I go to a console (CTRL+ALT+F1) and kill -9 the process: ----- Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb716f6d0 (LWP 20447)] 0xb789d6eb in ?? () from /lib/i686/cmov/libc.so.6 (gdb) (gdb) bt #0 0xb789d6eb in ?? () from /lib/i686/cmov/libc.so.6 Cannot access memory at address 0xbfb026e0 (gdb) > Can you also try to rename your ~/.xmoto directory to something else. Now, that fixed this for me. My ~/.xmoto was created before having upgrading xmoto from etch to lenny, so it probably has the wrong format... Do you want me to make a tarball with the old .xmoto tarball? Even if I suppose that if you just install etch's version, run it and then upgrade to lenny you'll be able to reproduce this... Well, anyway, feel free to ask me to do any tests you want to get this issue fixed... Thank you, -- Marcos Marado -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
