Re: How to confirm a memory leak

Hi; On 30 July 2016 at 14:58, wrote: > You need to set the malloc routines to use the real system malloc; > > export G_DEBUG=gc-friendly > export G_SLICE=always-malloc With recent (2 years old at least) versions of GLib, `G_SLICE=always-malloc` is not

gtk+-3.20 DnD x11 issues

Hi all, A good deal of changes went into gdkdnd-x11.c from gtk+-3.18 to gtk+-3.20. And now my application which works fine with gtk+-3.18 crashes when a dnd operation starts. I tried to enable deprecated code which works fine when building with gtk+-2.24, but it crashes just the same. I've

Re: How to confirm a memory leak

Hi; On 30 July 2016 at 20:00, Norman Goldstein wrote: > It seems the debug version is less confusing for valgrind, or > >*** Does the debug code actually present different source code to the > compiler? Yes; debugging code enables various code paths that are meant to

Re: How to confirm a memory leak

Thank you for this. I have attached the source for the code being tested. The valgrind report, attached, was greatly pared down, as a consequence of your suppression file. I ran valgrind twice: 1st time: No debug info -- 519 bytes definitely lost 2nd time: With debug info -- 7 bytes