Just a short update on GIT changes here: - checked in Delay Audio plugin changes after a lot of changes. See BT #638 for more details: https://www.cinelerra-gg.org/bugtracker/view.php?id=638 - removed previous library versions of tiff, flac, libjpeg-turbo and libvpx so download is smaller again.
I don't see any BT #638 in Mantis BT. What am I doing wrong? IgorBeg Il 25/05/2023 18:57, Phyllis Smith via Cin ha scritto:
Just a short update on GIT changes here: - checked in Delay Audio plugin changes after a lot of changes. See BT #638 for more details: https://www.cinelerra-gg.org/bugtracker/view.php?id=638 - removed previous library versions of tiff, flac, libjpeg-turbo and libvpx so download is smaller again.
After the last maintenance done, we have to log in with our own account to see the new issues. I also used to not log in, but it's better this way, for security and spam reasons.
After log in in Mantis BT, same problem: I don't see any BT#638. The max issue number, I can see, is #637. It is strange. May be that only Administrator(s) can see that issue? IgorBeg Il 26/05/2023 10:30, Andrea paz ha scritto:
After the last maintenance done, we have to log in with our own account to see the new issues. I also used to not log in, but it's better this way, for security and spam reasons.
Igor I am sorry it took me so long to fix this -- I had never done that before and THANK you so much for analyzing the cause of the issue. It had "view status" as Private instead of Public. You should be able to see it now. ...Phyllis On Sat, May 27, 2023 at 1:33 AM Igor BEGHETTO via Cin < [email protected]> wrote:
After log in in Mantis BT, same problem: I don't see any BT#638. The max issue number, I can see, is #637. It is strange. May be that only Administrator(s) can see that issue? IgorBeg
Il 26/05/2023 10:30, Andrea paz ha scritto:
After the last maintenance done, we have to log in with our own account to see the new issues. I also used to not log in, but it's better this way, for security and spam reasons.
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
сб, 27 мая 2023 г., 17:34 Phyllis Smith via Cin <[email protected]
:
Igor I am sorry it took me so long to fix this -- I had never done that before and THANK you so much for analyzing the cause of the issue. It had "view status" as Private instead of Public. You should be able to see it now. ...Phyllis
It also appeared for me, so I've read this whole discussion for first time! It still sad Andrea's cingg still crash ... :( Andrea, can you point gdb at cin executable, run it inside gdb and post backtrace? ( I am not very good at reading dmp files :/)
On Sat, May 27, 2023 at 1:33 AM Igor BEGHETTO via Cin < [email protected]> wrote:
After log in in Mantis BT, same problem: I don't see any BT#638. The max issue number, I can see, is #637. It is strange. May be that only Administrator(s) can see that issue? IgorBeg
Il 26/05/2023 10:30, Andrea paz ha scritto:
After the last maintenance done, we have to log in with our own account to see the new issues. I also used to not log in, but it's better this way, for security and spam reasons.
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Andrea, can you point gdb at cin executable, run it inside gdb and post backtrace? ( I am not very good at reading dmp files :/)
I'm sorry but I don't understand how to do it with gdb. Years ago I tried following GG's instructions. Now I have done the copy/paste of the instructions again but, when launching CinGG inside gdb I get: (gdb) run /tmp/cinelerra-5.1/bin/./cin Starting program: /tmp/cinelerra-5.1/bin/./cin No executable file specified. Use the "file" or "exec-file" command. (gdb) I have no idea what to do (also because I don't know what I did...). Try to give me a list of instructions on how to do it. PS: the GG's istruction are these: Are you able to build from source with full debugging symbols?
Yes, the easy way to get a full static (non-debug) build is to: # git clone ... # cp -a /path/cinelerra-5.1 /tmp/ # cd /tmp/cinelerra-5.1 # ./bld.sh Then, to run as a developer in the debugger: # CFLAGS=-ggdb make -j16 rebuild_all # cd /tmp/cinelerra-5.1/bin # gdb (gdb) handle SIG32 pass nostop noprint (gdb) set pa off (gdb) run /tmp/cinelerra-5.1/bin/./cin
вс, 28 мая 2023 г., 10:19 Andrea paz <[email protected]>:
Andrea, can you point gdb at cin executable, run it inside gdb and post backtrace? ( I am not very good at reading dmp files :/)
I'm sorry but I don't understand how to do it with gdb. Years ago I tried following GG's instructions. Now I have done the copy/paste of the instructions again but, when launching CinGG inside gdb I get:
(gdb) run /tmp/cinelerra-5.1/bin/./cin Starting program: /tmp/cinelerra-5.1/bin/./cin No executable file specified. Use the "file" or "exec-file" command. (gdb)
I have no idea what to do (also because I don't know what I did...). Try to give me a list of instructions on how to do it.
I just use 'gdb cin' and then 'run' from inside gdb.. It might stop at some gui interaction, then I go to terminal with gdb and print 'c' continue there ...
PS: the GG's istruction are these:
Are you able to build from source with full debugging symbols?
Yes, the easy way to get a full static (non-debug) build is to: # git clone ... # cp -a /path/cinelerra-5.1 /tmp/ # cd /tmp/cinelerra-5.1 # ./bld.sh
Then, to run as a developer in the debugger: # CFLAGS=-ggdb make -j16 rebuild_all # cd /tmp/cinelerra-5.1/bin # gdb (gdb) handle SIG32 pass nostop noprint (gdb) set pa off (gdb) run /tmp/cinelerra-5.1/bin/./cin
Thanks, with your instructions gdb worked. I couldn't get a log though. I attach part of what appeared on the terminal. In any case I didn't crash with delay_audio and everything worked fine. I don't know why.
Andrea, so it no longer crashes for you is my understanding? I think something may have gotten reset -- kind of like a "rebuild index" that solved the problem. And so when you first added the patch, it was not reset for some reason. All is well that ends well. On Sun, May 28, 2023 at 1:46 AM Andrea paz <[email protected]> wrote:
Thanks, with your instructions gdb worked. I couldn't get a log though. I attach part of what appeared on the terminal. In any case I didn't crash with delay_audio and everything worked fine. I don't know why.
I did some more testing and now the patch works and I haven't had any more crashes. The only difference is that before compiling I deleted the old .bcast folder. So that was where something was wrong. Sorry for wasting your time on my mistake.
Andrea, I use the manual instructions: https://cinelerra-gg.org/download/CinelerraGG_Manual/Debuggable_Single_User_... so the only lines you have to change are instead of "cd /tmp/cinelerra-5.1/bin" just "cd cinelerra" (since you are already in the cinelerra path" and the next line of "gdb" should be "gdb ./ci". Then all I do when it comes up is keyin "r" for run and then CinGG windows come up. The only other thing to know is that when it crashes, the windows freeze and you should go back to the startup window where it shows the crash line and type in "bt" which is the useful backtrace. On Sun, May 28, 2023 at 1:19 AM Andrea paz <[email protected]> wrote:
Andrea, can you point gdb at cin executable, run it inside gdb and post backtrace? ( I am not very good at reading dmp files :/)
I'm sorry but I don't understand how to do it with gdb. Years ago I tried following GG's instructions. Now I have done the copy/paste of the instructions again but, when launching CinGG inside gdb I get:
(gdb) run /tmp/cinelerra-5.1/bin/./cin Starting program: /tmp/cinelerra-5.1/bin/./cin No executable file specified. Use the "file" or "exec-file" command. (gdb)
I have no idea what to do (also because I don't know what I did...). Try to give me a list of instructions on how to do it.
PS: the GG's istruction are these:
Are you able to build from source with full debugging symbols?
Yes, the easy way to get a full static (non-debug) build is to: # git clone ... # cp -a /path/cinelerra-5.1 /tmp/ # cd /tmp/cinelerra-5.1 # ./bld.sh
Then, to run as a developer in the debugger: # CFLAGS=-ggdb make -j16 rebuild_all # cd /tmp/cinelerra-5.1/bin # gdb (gdb) handle SIG32 pass nostop noprint (gdb) set pa off (gdb) run /tmp/cinelerra-5.1/bin/./cin
Great Phyllis! Now, I can see the BT#638 in MantisBT. Thanks! Il 27/05/2023 16:34, Phyllis Smith ha scritto:
Igor I am sorry it took me so long to fix this -- I had never done that before and THANK you so much for analyzing the cause of the issue. It had "view status" as Private instead of Public. You should be able to see it now. ...Phyllis
On Sat, May 27, 2023 at 1:33 AM Igor BEGHETTO via Cin <[email protected] <mailto:[email protected]>> wrote:
After log in in Mantis BT, same problem: I don't see any BT#638. The max issue number, I can see, is #637. It is strange. May be that only Administrator(s) can see that issue?
participants (4)
-
Andrea paz -
Andrew Randrianasulu -
Igor BEGHETTO -
Phyllis Smith