Re: ListStoreModel clear() seems to be corrupted nearby memory
- From: Paul Davis <paul linuxaudiosystems com>
- To: Murray Cumming <murrayc murrayc com>
- Cc: Josh Sinykin <jsinykin gmail com>, gtkmm-list <gtkmm-list gnome org>
- Subject: Re: ListStoreModel clear() seems to be corrupted nearby memory
- Date: Thu, 20 Dec 2007 19:02:47 -0500
On Thu, 2007-12-20 at 19:45 +0100, Murray Cumming wrote:
> On Thu, 2007-12-20 at 11:36 -0700, Josh Sinykin wrote:
> > I figured it out.
> >
> > I think this might have been broken in previous gtkmm builds (2.10 and
> > lower), just recently moved to 2.12....
> >
> > I have the combo box with the listStore connected to a function using
> > signal_changed().connect();
> >
> > When I call clear() on the ListStore model reference, the
> > signal_changed function is being called which in my instance was
> > clearing the memory. This was unexpected and thus why I thought it
> > looked like memory corruption and why valgrind did not flag it.
> >
> > is there a list of reasons why certain signals are called in relation
> > to model api calls?
>
> Not really, and I wish there was. Do file bugs against GTK+ for any
> signals that don't seem sufficiently documented, though the chances of
> them being documented are slim, I'm afriad.
in this particular case, this was an advertised change in the semantics
of a GtkComboBox sometime between Gtk+ 2.8 and 2.11. it caused crashes
in my code too, until i realized what was going on.
--p
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]