Am 08.09.2012 00:41, schrieb AV Linux: > signal_entry: got SIGSEGV my pid=16486 execution table size=0:
doesn't reveal any usable information, unfortunately. The only way to find out what is breaking would be to run with a debugger and try to reproduce the segmentation error; this would reveal the actual source line where the crash happens and would at least allow a guess what feature is broken. I'm aware that you'd need some coding / developer skills to conduct that procedure (i.e. being able to create a build with source line information included), but when a piece of software doesn't provide any built-in diagnostics, there aren't much alternatives left. Cheers, Hermann V. _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
