Re: [Cin] Valgrind

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

Re: [Cin] Valgrind

[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 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.


Val3-gdb.tar.gz
Description: application/gzip
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Valgrind

[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 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:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word".
> (gdb) handle SIG32 pass nostop noprint
> SignalStop  Print   Pass to program Description
> SIG32 NoNo  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
>
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Valgrind

[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 Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
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:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) handle SIG32 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG32 NoNo  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"?


val2.tar.gz
Description: application/gzip
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Valgrind

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


gdbinit
Description: Binary data
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Valgrind

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

Re: [Cin] Valgrind

[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 /tmp/cinelerra-5.1/cinelerra-5.1/bin/./cin
Starting program: /tmp/cinelerra-5.1/cinelerra-5.1/bin/cin 
/tmp/cinelerra-5.1/cinelerra-5.1/bin/./cin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Cinelerra Infinity - built: May 15 2020 10:35:01
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG by W.P.Morrow aka goodguy
Cinelerra is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. There is absolutely no warranty for Cinelerra.

[New Thread 0x730d5700 (LWP 326965)]
[Detaching after vfork from child process 326966]
[New Thread 0x72864700 (LWP 326969)]
[New Thread 0x72063700 (LWP 326970)]
[New Thread 0x71862700 (LWP 326971)]
[New Thread 0x71061700 (LWP 326972)]
[New Thread 0x70860700 (LWP 326973)]
[New Thread 0x7005f700 (LWP 326974)]
[New Thread 0x7fffef85e700 (LWP 326975)]
[New Thread 0x7fffef05d700 (LWP 326976)]
[New Thread 0x7fffee85c700 (LWP 326977)]
[New Thread 0x7fffee05b700 (LWP 326978)]
[New Thread 0x7fffed85a700 (LWP 326979)]
[New Thread 0x7fffed059700 (LWP 326980)]
[New Thread 0x7fffec858700 (LWP 326981)]
[New Thread 0x7fffe7fff700 (LWP 326982)]
[New Thread 0x7fffe77fe700 (LWP 326983)]
[New Thread 0x7fffe6ffd700 (LWP 326984)]
[New Thread 0x7fffe67fc700 (LWP 326985)]
[New Thread 0x7fffe5ffb700 (LWP 326986)]
[New Thread 0x7fffe57fa700 (LWP 326987)]
[New Thread 0x7fffe4ff9700 (LWP 326988)]
[New Thread 0x7fffdbfff700 (LWP 326989)]
[New Thread 0x7fffdb7fe700 (LWP 326990)]
[New Thread 0x7fffdaffd700 (LWP 326991)]
[New Thread 0x7fffda7fc700 (LWP 326992)]
[Thread 0x730d5700 (LWP 326965) exited]
[New Thread 0x7fffcbfff700 (LWP 326995)]
[New Thread 0x730d5700 (LWP 326993)]
[New Thread 0x7fffd8d63700 (LWP 326994)]
[New Thread 0x7fffca7fc700 (LWP 326998)]
[New Thread 0x7fffcb7fe700 (LWP 326997)]
[New Thread 0x7fffcaffd700 (LWP 326996)]
[New Thread 0x7fffc9ffb700 (LWP 326999)]
[New Thread 0x7fffc97fa700 (LWP 327000)]
[New Thread 0x7fffabfff700 (LWP 327002)]
[New Thread 0x7fffab7fe700 (LWP 327003)]
[New Thread 0x7fffc880f700 (LWP 327001)]
[New Thread 0x7fffaa7fc700 (LWP 327005)]
[New Thread 0x7fffa9ffb700 (LWP 327006)]
[New Thread 0x7fffaaffd700 (LWP 327004)]
[New Thread 0x7fffa3fff700 (LWP 327009)]
[New Thread 0x7fffa8ff9700 (LWP 327008)]
[New Thread 0x7fffa97fa700 (LWP 327007)]
[New Thread 0x7fffa2ffd700 (LWP 327010)]
[New Thread 0x7fffa37fe700 (LWP 327011)]
[New Thread 0x7fffa27fc700 (LWP 327012)]
FFMPEG::open_decoder: some stream have bad times: 
/home/paz/video_editing/prova/1080/bbb-splash.png
[New Thread 0x7fffa1ffb700 (LWP 327013)]
[New Thread 0x7fffa17fa700 (LWP 327014)]
[New Thread 0x7fffa0ff9700 (LWP 327015)]
[New Thread 0x7fff93fff700 (LWP 327016)]
[New Thread 0x7fff937fe700 (LWP 327017)]
[New Thread 0x7fff92ffd700 (LWP 327018)]
[New Thread 0x7fff927fc700 (LWP 327019)]
[New Thread 0x7fff91ffb700 (LWP 327020)]
[New Thread 0x7fff90c06700 (LWP 327021)]
[New Thread 0x7fff67fff700 (LWP 327022)]
[New Thread 0x7fff677fe700 (LWP 327023)]
[New Thread 0x7fff66ffd700 (LWP 327024)]
[New Thread 0x7fff667fc700 (LWP 327025)]
[New Thread 0x7fff65ffb700 (LWP 327026)]
[New Thread 0x7fff657fa700 (LWP 327027)]
[New Thread 0x7fff64ff9700 (LWP 327028)]
[New Thread 0x7fff5f40b700 (LWP 327029)]
[New Thread 0x7fff5ec0a700 (LWP 327030)]
[New Thread 0x7fff5e409700 (LWP 327031)]
[New Thread 0x7fff5dc08700 (LWP 327032)]
[New Thread 0x7fff5d407700 (LWP 327033)]
[New Thread 0x7fff5cc06700 (LWP 327034)]
[New Thread 0x7fff3700 (LWP 327035)]
[New Thread 0x7fff3f7fe700 (LWP 327036)]
[Thread 0x7fffcaffd700 (LWP 326996) exited]
[New Thread 0x7fffcaffd700 (LWP 327037)]
[New Thread 0x7fff3ea0e700 (LWP 327038)]
[New Thread 0x7fff3e20d700 (LWP 327039)]
[Thread 0x730d5700 (LWP 326993) exited]
Decoder png does not support device type vdpau.
HW device init failed, using SW decode.
file:/home/paz/video_editing/prova/1080/bbb-splash.png
 err: Operazione non permessa
[New Thread 0x7fff3ce18700 (LWP 327040)]
[New Thread 0x7fff1700 (LWP 327041)]
[New Thread 0x7fff1f7fe700 (LWP 327042)]
[New Thread 0x7fff1effd700 (LWP 327043)]
[New Thread 0x7fff1e7fc700 (LWP 327044)]
[New Thread 0x7fff1dffb700 (LWP 327045)]
[New Thread 0x7fff1d7fa700 (LWP 327046)]
[New Thread 0x7fff1cff9700 (LWP 327047)]
[Thread 0x7fffcb7fe700 (LWP 326997) exited]
[Thread 0x7fffd8d63700 (LWP 326994) exited]
[New Thread 0x730d5700 (LWP 327048)]
[New Thread 0x7fffd8d63700 (LWP 327049)]
[New Thread 0x7fffcb7fe700 (LWP 327050)]
--Type  for more, q to quit, c to continue without paging--c
[I pressed "c" key]
Thread 83 "cin" received signal 

Re: [Cin] Valgrind

[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 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.
> 


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Valgrind

[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

[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
is fixed so try to avoid Ctrl-C and use a normal Quit instead.

Add:
  --num-callers=32  (the default is 12 so texture leaking does not
point to far enough to see the problem)
  --leak-check=full

On Sun, Jun 30, 2019 at 2:11 AM Andrea paz 
wrote:

> To thank you for the enormous developments you continue to bring, I
> have made a "valgrind" that I hope will be useful.
> I've played a little with masks, with Gradient and with Sketcher. In
> the latter I caused the freeze with the color picker and then I came
> out with CTRL+C causing the creation of a dump.
> I used as settings in Preferences: Vdpau and OpenGL.
> --
> Cin mailing list
> Cin@lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin