[Gambas-user] Weird Timer Problem

[Benoit Minisini]

On dimanche 20 janvier 2008, Gareth Bult wrote:
> Mmm, yes ...
>
> But I think you're going to tell me I need to do something else to get more
> information out ??
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1210841424 (LWP 25197)]
> 0x10aa5600 in ?? ()
> (gdb) bt
> #0  0x10aa5600 in ?? ()
> #1  0xb70b8506 in ?? () from /usr/lib/libglib-2.0.so.0
> #2  0x082526a8 in ?? ()
> #3  0x08334e80 in ?? ()
> #4  0xbf9c81c8 in ?? ()
> #5  0xb70b76b8 in ?? () from /usr/lib/libglib-2.0.so.0
> #6  0xb712e804 in ?? () from /usr/lib/libglib-2.0.so.0
> #7  0xbf9c81cc in ?? ()
> #8  0xbf9c81d8 in ?? ()
> #9  0xb712e248 in ?? () from /usr/lib/libglib-2.0.so.0
> #10 0xb712e248 in ?? () from /usr/lib/libglib-2.0.so.0
> #11 0xbf9c820c in ?? ()
> #12 0xbf9c8228 in ?? ()
> #13 0xb70b7d96 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
> Backtrace stopped: frame did not save the PC
>

Did you compile Gambas with the debugging informations? To do that, you must 
use 'make "CFLAGS=-O0 -g" "CXXFLAGS=-O0 -g"' instead of just 'make'.

Can you try with gb.qt instead of gb.gtk too?

Regards,

-- 
Benoit Minisini