On Wed, 2011-11-23 at 18:07 +, Thomas Harty wrote:
> I'll see if I can narrow down exactly what's causing this...
Still, looks like you're pretty close to a good suppression file.
Where should we install it?
/usr/share/suppression/glib.sup
/usr/share/suppression/gtk.sup
sorry, mistake when copying and pasting, that should have been:
==3291== 20 bytes in 1 blocks are definitely lost in loss record 5,225 of 10,005
==3291==at 0x4028876: malloc (vg_replace_malloc.c:236)
==3291==by 0x4E0D80A: standard_malloc (gmem.c:88)
==3291==by 0x4E0DD61: g_malloc (gmem
Hi Tom,
On 23 November 2011 15:21, Thomas Harty wrote:
> any suggestions for what's causing this leak report and the best way to
> suppress it?
That looks like a gtk/gtkmm bug to me, but it's hard to tell without
some context. Could you make a tiny test program which shows this
behaviour?
It a
I've been updating the suppression file to work with the new version of Gtk.
I'm getting a few errors for widgets which are deleted by Gtk (using the manage
function), which look like this (N.B. it's actually a Gtkmm app):
==13910== 20 bytes in 1 blocks are definitely lost in loss record 5,230 o
I've been updating the suppression file to work with the new version of Gtk.
I'm getting a few errors for widgets which are deleted by Gtk (using the manage
function), which look like this:
From: gtk-app-devel-list-boun...@gnome.org
[gtk-app-devel-list-b
Hi,
I'm facing the same problem, which version of glib are you using ? I'm using
the 2.28.8, and I'm working on embedded ARM device.
I tried to run the test gdbus-serialization, first on my computer (x86_64)
and there is no problem.
Then I run it on the target I'm working on (armv5tejl), and I go
>> -> Windows portability for gnome software
>> (http://www.iki.fi/tml/fosdem-2006.pdf)
>
> I don't know this useful presentation before, Thanks.
I have spent weeks trying to debug a gtk-win32 application with threads
until I finally discovered this one and modified the code. ;)
--
Emmanuel Tho
On Wed, Nov 23, 2011 at 4:16 PM, Emmanuel Thomas-Maurin
wrote:
> On 11/23/2011 07:28 AM, KC wrote:
>> On Wed, Nov 23, 2011 at 12:43 PM, Michael Cronenworth
>> wrote:
>>> On 11/22/2011 10:13 PM, KC wrote:
So the "Unfortunately ..." statement only apply to GDK on WIN32 ?
It's safe t
On 11/23/2011 07:28 AM, KC wrote:
> On Wed, Nov 23, 2011 at 12:43 PM, Michael Cronenworth wrote:
>> On 11/22/2011 10:13 PM, KC wrote:
>>>
>>> So the "Unfortunately ..." statement only apply to GDK on WIN32 ?
>>> It's safe to call GTK+ APIs (if protected by gdk_threads_enter/leave)
>>> from multi-t
