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 not start CinGG. How to do it? PS2: I also take this opportunity to thank Sergio for the optimizations and improvements he makes to the manual.
В сообщении от 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 not start CinGG. How to do it?
Just type 'run' inside gdb shell ? (and add any cmd line parameters there, too, if you need them ...)
PS2: I also take this opportunity to thank Sergio for the optimizations and improvements he makes to the manual.
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."
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 in as Andrew said: run (or simply r) What GG does is he keeps a .gdbinit file in his home directory so that he does not have to type in the handle and set lines over and over again as he does a lot of debugging. The file, .gdbinit, is a hidden file so starts with the "." and the one he uses is attached here. On Fri, May 15, 2020 at 7:26 AM Andrea paz <[email protected]> wrote:
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." -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
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 Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) handle SIG32 pass nostop noprint Signal Stop Print Pass to program Description SIG32 No No Yes Real-time event 32 (gdb) set pa off (gdb) run /tmp/cinelerra-5.1/cinelerra-5.1/bin/./cin Starting program: /tmp/cinelerra-5.1/cinelerra-5.1/bin/./cin No executable file specified. Use the "file" or "exec-file" command. (gdb) I'm too incompetent to understand anything, I'm sorry. I used the command to valgrind: # CFLAGS=-ggdb make -j16 rebuild_all To make a gdb we have to give the same command. I didn't give the command this second time thinking it was enough to give it first. Didn't I? Before doing a gdb is better to do a "make clean" and then again "./bld.sh" followed by "CFLAGS=-ggdb make -j16 rebuild_all"?
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 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. If you miss, then in Settings->Preferences, the Interface tab, you can "reload plugins" and that will load them again (and make sure you have valgrind going). To run gdb, this is how I do it. First do what you did:
Before doing a gdb is better to do a "make clean" and then again "./bld.sh" followed by "CFLAGS=-ggdb make -j16 rebuild_all"
0) you only have to do CFLAGS step one time after each bld.sh step 1) cd cinelerra_path/cinelerra 2) gdb ./ci (gdb) handle SIG32 pass nostop noprint (gdb) set pa off run Don't give up! Let us know where/if you get stopped again. But gdb still doesn't work:
[root@arch-paz bin]# gdb GNU gdb (GDB) 9.1 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later < http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) handle SIG32 pass nostop noprint Signal Stop Print Pass to program Description SIG32 No No Yes Real-time event 32 (gdb) set pa off (gdb) run /tmp/cinelerra-5.1/cinelerra-5.1/bin/./cin Starting program: /tmp/cinelerra-5.1/cinelerra-5.1/bin/./cin No executable file specified. Use the "file" or "exec-file" command. (gdb)
I'm too incompetent to understand anything, I'm sorry. I used the command to valgrind:
# CFLAGS=-ggdb make -j16 rebuild_all
To make a gdb we have to give the same command. I didn't give the command this second time thinking it was enough to give it first. Didn't I? Before doing a gdb is better to do a "make clean" and then again "./bld.sh" followed by "CFLAGS=-ggdb make -j16 rebuild_all"? -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
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.
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 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 <[email protected]> wrote:
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 [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
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 not generate these same errors on Fedora so he updated our Arch system and tried it there and still could not. However, if you have some spare time in the future, could you replace the 2 files I will send in a separate email to just you, build with these 2 and then run Valgrind again (you only have to get past the lv2 plugin loads so not as time-consuming)? This will let us know if that modification he added to these 2 files fixes the original problem so that there are no more "invalid reads". Let me know if this makes sense or if there is a problem. On Fri, May 15, 2020 at 2:59 AM Andrea paz <[email protected]> wrote:
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 not start CinGG. How to do it?
PS2: I also take this opportunity to thank Sergio for the optimizations and improvements he makes to the manual. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith