[Cin] Valgrind

Phyllis Smith phylsmith2017 at gmail.com
Sun May 17 20:28:47 CEST 2020

GG says to make sure to say "thank you!".  You are able to find problems on
Arch that he does not see on Fedora.  So as you probably already noted from
the GIT checkin, at least 4 valgrind errors your logs pointed to have now
been fixed.  This last valgrind log has no additional errors reported in
it, so I guess that the mod for lv2 plugins fixed the "invalid read"
error.  Will let you know next time gg wants a general or specific valgrind
- probably after he gets to phase 2 of audio which we are struggling with.

Also, glad you got gdb working as it will come in handy in the future
should you get a crash.  For some reason I had thought that some png's did
work with vdpau hardware acceleration (never mind, it was vaapi where some
png's and jpg's work per the release notes so I guess vdpau never did?)
P.S. I do NOT want to see your rodents.png file !!

On Sun, May 17, 2020 at 1:39 AM Andrea paz <gamberucci.andrea at gmail.com>

> >
> >When/if you have time could you do 1 more because the 2nd one you did
> already had the LV2 plugins loaded?  So the first time AFTER you did a
> build, when you run Cinelerra it will reload the >plugins so that is when
> you have to have Valgrind going.
> >
> Sorry, Phyllis; I understood the opposite (damn my English!).
> I put X11 in place of OpenGL and played with the tracks height and
> collect effects.
> I enclose the third Valgrind and also gdb, which I now understand how
> it works...
> If you are interested in a valgrind/gdb of any particular plugin or
> tool, let me know. With the new PC the compilation is only 5 min and
> even Valgrind is not extremely slow.
> --
> Cin mailing list
> Cin at lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20200517/b3d6bfbd/attachment.html>

More information about the Cin mailing list