Re: [Iup-users] CID 341016 (#1 of 1): Dereference after null check (FORWARD_NULL)

Committed a slighted changed version. Em sáb, 25 de mai de 2019 às 08:45, Ranier VF escreveu: > Hi, > Fix iup_globalattrib.c: > --- ..\..\a\src\iup_globalattrib.c Tue Apr 23 14:33:33 2019 > +++ iup_globalattrib.c Sat May 25 08:42:08 2019 > @@ -133,7 +133,7 @@ >iupdrvWarpPointer(x,

Re: [Iup-users] CID 210676 (#1 of 1): Resource leak (RESOURCE_LEAK)

The code you added is an unreachable code. The "for" never ends normally, only in the return. Em sáb, 25 de mai de 2019 às 08:28, Ranier VF escreveu: > Hi, > Fix RESOURCE_LEAK at iup_attrib.c > > --- ..\..\a\src\iup_attrib.cSat Jan 26 16:02:13 2019 > +++ iup_attrib.cSat May 25 08:25:

Re: [Iup-users] ENC: New Defects reported by Coverity Scan for IUP - Portable User Interface

I received the same message sent directly by Coverity Scan. Best, Scuri Em sáb, 25 de mai de 2019 às 08:08, Ranier VF escreveu: > Hi, > This a new report by Coverity about IUP 3.27 Windows port. > Best regards, > Ranier Vilela > > De: scan-ad...@cover

Re: [Iup-users] IUP 3.27: iupObjectCheck raise segmentation fault

It seems that is trying to destroy an IupImage that is already destroyed. I can't go further without more context. Can you reproduce the problem in a small sample? Best, Scuri Em sex, 24 de mai de 2019 às 16:33, Ranier VF escreveu: > Hi, > I'm around with a IUP bug. Below show the callsta

[Iup-users] Follow-up on Holzmann@JPL, Coverity and Tecgraf tools...

G'day, [Cross-posting again to lua-l, as I have some questions about code coverage (e.g. Valgrind), and I believe that the IM/CD/IUP modules are only a short distance away from achieving a significantly higher level of "Code Cleanliness" -- but this goal needs help from the community.] I've seen