Re: [Cin] Valgrind

2020-05-17 Thread Phyllis Smith
Andrea, 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

Re: [Cin] Valgrind

2020-05-17 Thread Andrea paz
> >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

Re: [Cin] Valgrind

2020-05-16 Thread Phyllis Smith
Andrea, GG checked into GIT the changes as was in the 2 files sent yesterday along with 4 fixes that came out of your Valgrinds so that is a really good thing. Each valgrind produced results for improvement. When/if you have time could you do 1 more because the 2nd one you did already had the

Re: [Cin] Valgrind

2020-05-16 Thread Andrea paz
I enclose the new Valgrind, made after the replacement of pluginlv2.C and pluginlv2.h I played a bit with the height of the tracks and also with "collects effects" and "paste effects". But gdb still doesn't work: [root@arch-paz bin]# gdb GNU gdb (GDB) 9.1 Copyright (C) 2020 Free Software

Re: [Cin] Valgrind

2020-05-15 Thread Phyllis Smith
Andrea, thanks for including the gdb.txt file as it pointed to the problem. To fix the problem, at the first gdb prompt, keyin: handle SIG32 pass nostop noprint You might also want to keyin next: set pa off because then you do not have to keep typing "c" as a page fills up. Next just type

Re: [Cin] Valgrind

2020-05-15 Thread Phyllis Smith
Andrea, Thanks very much for running Valgrind -- it is appreciated as I do not have patience enough to run it. From this GG was able to find 2 fixes for lost bytes in performanceprefs.C and edl.C. There is also a mysterious report of "invalid read of size 4" when loading LV2 plugins. He could

Re: [Cin] Valgrind

2020-05-15 Thread Andrea paz
Thank you for the "run" advice. The first time I gave "run ..." it started CinGG but opened a window of the audio format and when I gave OK I crashed and I killed the application. Other tests of "run ..." no longer work: "No executable file specified." (gdb) run

Re: [Cin] Valgrind

2020-05-15 Thread Andrew Randrianasulu
В сообщении от Friday 15 May 2020 11:59:41 Andrea paz написал(а): > To thank GG, I offer a Valgrind made with the new release, with the > modifiability of the audio track height. > > PS1: I also tried to run CinGG with gdb (# gdb ./cin) but it opens the > gdb shell waiting for commands and does

Re: [Cin] Valgrind

2019-07-01 Thread Andrea paz
I made a new Valgrind. I still used Vdpau, which gave several errors on the terminal. Anyway everything OK. val.tar.gz Description: application/gzip -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Valgrind

2019-07-01 Thread Phyllis Smith
Andrea, thank you. GG is looking at it now. There is a lot of leaking in textures of OpenGL. If/when you have time to rerun, it would be helpful if you add the following 2 additional parameters so maybe it will help to pinpoint the texture leak problem. Also, the color picker in the Sketcher