Re: Event loop hangup when using TimeoutSource and IdleSource

[Jim Hodapp <james hodapp gmail com>]

Chris,

    Yes, I didn't notice that until you pointed that out. I'm going  
to try and hunt this issue down. It must have to do with timing of  
when things go out of scope and might explain why things seem random  
in general.

Also, you mentioned the boost signals2 library. How do you use this  
library instead of sigc with glibmm objects like Glib::IdleSource or  
Glib::TimeoutSource. They seem to want sigc slots specifically.

Thanks,

Jim

On Sep 24, 2009, at 5:42 PM, Chris Vine wrote:

> On Thu, 24 Sep 2009 16:43:21 -0400
> Jim Hodapp <james hodapp gmail com> wrote:
> >     I removed the inheritance statement from my Emsac class
> > definition and things seemed more stable. Things remained stable
> > until I moved the mouse over some widgets in the main window that
> > will accept focus and very shortly after that the application
> > segfaulted. The backtrace is as follows:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0xb6bbd720 (LWP 26118)]
> > 0xb7c3b439 in Gtk::Label::set_text (this=0x0, str= 0xbfd5ad88) at
> > label.cc:252
> > 252     label.cc: No such file or directory.
> >         in label.cc
> > (gdb) bt
> > #0  0xb7c3b439 in Gtk::Label::set_text (this=0x0, str= 0xbfd5ad88)
> > at label.cc:252
>
> Jim,
>
> Having finished with threads, which seem irrelevant to this, you will
> notice that this crash is caused by a call on a null pointer argument
> for a Gtk::Label object.  You still seem to have an object lifetime
> issue.  The label doesn't seem to exist when the idle handler  
> executes.
>
> Chris