Re: ListStoreModel clear() seems to be corrupted nearby memory
- From: "Josh Sinykin" <jsinykin gmail com>
- To: "Murray Cumming" <murrayc murrayc com>
- Cc: gtkmm-list <gtkmm-list gnome org>
- Subject: Re: ListStoreModel clear() seems to be corrupted nearby memory
- Date: Thu, 20 Dec 2007 11:36:01 -0700
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?
Thanks again for all the help,
Josh Sinykin
On Dec 20, 2007 10:49 AM, Murray Cumming <murrayc murrayc com> wrote:
>
> On Thu, 2007-12-20 at 10:44 -0700, Josh Sinykin wrote:
> > Ok, using the cast_dynamic I get the same behavior. The clear
> > operation is clearing the static matrix array of std::string. Valgrind
> > has not flagged anything when I execute this code. But I can see the
> > results in DDD that this memory is being cleared on me.
>
> I'm quite sure that this is an error in your code, so could you try to
> create a simple-as-possible compilable test case that shows the problem?
> I mean simple as possible.
>
> And please use reply-to-all so that your reply goes to the list.
>
> --
>
> murrayc murrayc com
> www.murrayc.com
> www.openismus.com
>
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]