[Cin] Update on GIT changes

Phyllis Smith phylsmith2017 at gmail.com
Sun May 28 18:03:28 CEST 2023

Andrea, I use the manual instructions:

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 <gamberucci.andrea at gmail.com>

> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20230528/38d5e1c1/attachment.htm>

More information about the Cin mailing list