Scuri, Many thanks for the link and diagnosing the problem. I can confirm the valgrind messages do look to be referring to GTK. Unfortunately trying various combinations of flags suggested on the linked page and a few others has not fixed the problem. If it is not too much trouble can you please let me have the combination of flags that works for you,
regards, Andy. On Thu, 21 Feb 2019 at 16:29, Antonio Scuri <antonio.sc...@gmail.com> wrote: > > Hi, > > No problem. Valgrind has some issues with GTK. We use it here too. Please > take a look at this page: > > https://wiki.gnome.org/Valgrind > > Best, > Scuri > > > Em qui, 21 de fev de 2019 às 11:17, Honest Guvnor <honestguv...@gmail.com> > escreveu: >> >> Hi, >> >> Ubuntu 16.04.5 LTS 64-bit >> IUP 3.21 built from sources. >> valgrind 3.11.0 >> >> When running the small hello world example valgrind is reporting less >> than 40% of the memory allocated being freed by IupClose(). Is this >> expected behaviour? Is valgrind confused or is the memory genuinely >> not being freed? Has iup and/or valgrind been fixed in later versions >> of the software? >> >> I am getting on nicely with iup and so apologies for the somewhat >> negative opening post, >> >> regards, >> >> Andy. >> >> >> _______________________________________________ >> Iup-users mailing list >> Iup-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/iup-users > > _______________________________________________ > Iup-users mailing list > Iup-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/iup-users _______________________________________________ Iup-users mailing list Iup-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iup-users
