Kdenlive quality projects

[Eugen Mohr]

Hi all

On Windows, craft build Kdenlive with .debug files. So when I reproduce
the crash with gdb I get a backlog file. But the .debug files are huge.
Download the debug symbols dynamically would be a good idea.

Eugen


Am 28.09.2022 um 14:21 schrieb Vincent Pinon:
> Le 28/09/2022 à 12:47, Julius Künzel a écrit :
>> For Windows we need to look into re-enabling Dr. MinGW. It was
>> disabled since Craft used a MinGW version that was not compatible
>> with Dr. MinGW, but since a few month Craft uses MinGW 11 and it
>> should be possible to re-enable it.
>> Better logging of rendering crashes in the way you mentioned doesn't
>> seem that hard to implement, but very effective and useful. We have
>> many reports about rendering crashes without useful info to fix or
>> debug the cause.
>
> Hello,
>
> I agree with what stated before :
>
> 3) for tests : we should write more (including some UI but not with
> virtual display), but not investing years focusing on coverage, just
> adding little by little
>
> 2) for project test suite, but can run only before release by beta
> testers
>
> 1) for crash backtrace, trying to figure out how to dynamically
> download debug symbols (can we have something generic like abrt on
> fedora, whoopsie on ubuntu ?)
> also note that KCrash(DrKonqi) / DrMingw can currently be loaded only
> for kdenlive but not melt => for rendering crash info we must plug it
> into melt!
>
> Thanks for your involvement, good luck :-)
>
> Vincent
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20220928/a424cf0c/attachment-0001.htm>