I've already signaling the issue between selection and toggle cell :
here is the answer by kris
If the column is sorted, when one activates the toggle, the tree is
re-sorted (normal) but the selected row is changed (unexpected). I
investigated and I found that when clicking on a toggle cell
2010/1/1 Erik de Castro Lopo mle+...@mega-nerd.com:
- How does one go about teasing out the difference between my memory
leaks and GTK stuff I have no control over?
Just a few thoughts
Valgrind is an excellent product, and is designed for programmer use only.
It shows where
On Sat, Jan 2, 2010 at 4:20 AM, jcup...@gmail.com wrote:
2010/1/1 Erik de Castro Lopo mle+...@mega-nerd.com:
- How does one go about teasing out the difference between my memory
leaks and GTK stuff I have no control over?
I usually run my app twice: once with just startup/shutdown and
Bill C wrote:
Valgrind is an excellent product, and is designed for programmer use only.
It shows where unreleased memory was allocated, so one can trace each
chunk of memory to see if it should have been released, and take
appropriate action it your code allocated it.
That is easy when
Erik de Castro Lopo mle+...@mega-nerd.com wrote:
==12528== 27,300 bytes in 175 blocks are still reachable in loss record
11,194 of 11,196
==12528== at 0x4024C1C: malloc (vg_replace_malloc.c:195)
==12528== by 0x4B342E3: g_malloc (gmem.c:131)
==12528== by 0x4B4A418: g_slice_alloc
Dan Kegel wrote:
Erik de Castro Lopo mle+...@mega-nerd.com wrote:
==12528== 27,300 bytes in 175 blocks are still reachable in loss record
11,194 of 11,196
==12528== at 0x4024C1C: malloc (vg_replace_malloc.c:195)
==12528== by 0x4B342E3: g_malloc (gmem.c:131)
==12528== by
On Tue, Jan 05, 2010 at 09:39:48AM +1100, Erik de Castro Lopo wrote:
==12528== 27,300 bytes in 175 blocks are still reachable in loss record
11,194 of 11,196
==12528==at 0x4024C1C: malloc (vg_replace_malloc.c:195)
==12528==by 0x4B342E3: g_malloc (gmem.c:131)
==12528==by
On Mon, Jan 04, 2010 at 02:56:44PM -0800, Dan Kegel wrote:
Erik de Castro Lopo mle+...@mega-nerd.com wrote:
==12528== 27,300 bytes in 175 blocks are still reachable in loss record
11,194 of 11,196
==12528== at 0x4024C1C: malloc (vg_replace_malloc.c:195)
==12528== by 0x4B342E3:
