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
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin