Re: Re[4]: Does GTK leak memory

[Ankur Verma <ankurv2 gmail com>]

Greetings,

LS >>> By the way, is there any way to find out what the reference count of
LS >>> an object is?
LS > Experimental printf statements to dump ref counter values are good to
LS > understand which API function is adding a reference and which takes
LS > ownership.

G_OBJECT(gtk_widget)->ref_count

LS > And a tool that just dumps me which objects are still alive would be
LS > very helpfull too. MacOSX and MFC have features like this. Maybe GTK
Ls > is really just another toy?

GObject Refcount debugger: http://refdbg.sourceforge.net/

Regards,
Ankur

On Thu, Jun 3, 2010 at 2:06 AM, Lothar Scholz <llothar web de> wrote:
> Hello Emmanuele,
>
> Wednesday, June 2, 2010, 3:49:04 PM, you wrote:
>
> EB> On Wed, 2010-06-02 at 15:39 +0200, Lothar Scholz wrote:
>
>>> By the way, is there any way to find out what the reference count of
>>> an object is?
>
> EB> you really don't want to know that - because threads and
> EB> auto-vivification during dispose cycles might change that value beneath
> EB> your seat.
>
> I just want to catch up with the holes in the documentation.
> Experimental printf statements to dump ref counter values are good to
> understand which API function is adding a reference and which takes
> ownership. The total confusion in GTK about this serious topic
> (compared to Cocoa for example) is driving me crazy.
>
> And a tool that just dumps me which objects are still alive would be
> very helpfull too. MacOSX and MFC have features like this. Maybe GTK
> is really just another toy?
>
>
> --
> Best regards,
>  Lothar                            mailto:llothar web de
>
> _______________________________________________
> gtk-list mailing list
> gtk-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-list
>