Cannot build qt5-webkit with debug

[Michael Osipov]

Am 2020-02-24 um 19:10 schrieb Miroslav Lachman:
> Marcin Cieslak wrote on 2020/02/24 18:51:
>> On Mon, 24 Feb 2020, Marcin Cieslak wrote:
>>
>>> On Mon, 24 Feb 2020, Miroslav Lachman wrote:
>>>
>>>    frame #13: 0x00000008039aa3ed 
>>> libQt5WebKit.so.5`WebCore::CSSParser::parseSheet(this=0x00007fffffffa490, 
>>> sheet=0x00000008155f5e40, string=0x00007fffffffb888, 
>>> textPosition=0x00007fffffffb650, 
>>> ruleSourceDataResult=0x0000000000000000, logErrors=false) at 
>>> CSSParser.cpp:423:5
>>>
>>> Looks like it has some trouble parsing font declarations in the 
>>> HTML/CSS code you have been testing
>>> on. This can be a webkit bug...
>>>
>>> Would be good to have a minimal HTML/CSS testcase to reproduce this 
>>> and this should
>>> probably be reported upstream.
>>
>> There is this report:
>>
>> https://github.com/qtwebkit/qtwebkit/issues/933
>>
>> It says it crashes if you have no fonts installed (no TTF).
>>
>> Could this "fix" it?
> 
> Thank you for the tip, I will look at it.
> 
>
> This is the code of the tested example - fetching from 
> https://phantomjs.org/
> 
> (root at testjail) ~/# cat /tmp/phantom.2.js
> var page = require('webpage').create();
> page.onConsoleMessage = function(str) {
>     console.log(str);
> }
> page.open('https://phantomjs.org/api/phantom/', function(status) {
>     page.render('/tmp/beforeclick.png');
>     console.log(page.url);
> 
>     var element = page.evaluate(function() {
>        return document.querySelector('img[src = 
> "https://phantomjs.org/img/phantomjs-logo.png"]');
>     });
>     page.sendEvent('click', element.offsetLeft, element.offsetTop, 'left');
> 
>     window.setTimeout(function () {
>        console.log(page.url);
>        page.render('/tmp/afterclick.png');
>        phantom.exit();
>     }, 5000);
>     console.log('element is ' + element);
> });

Looking at your sample code and the website, there are several issues:

* The resource employs mixed site content HTTPS loads HTTP. Firefox 
blocks this, I guess WebKit blocks it too.
* Result: Droid Sans is not loaded [1], like the CSS
* The CSS has this:
> body {
>   font-family: 'Droid Sans','Lucida Grande',sans-serif;
>   line-height: 1.125em;
>   color: #444; }

Lucida Grande isn't there either. It must choke somewhere.

See also

> frame #10: 0x00000008039cf92c libQt5WebKit.so.5`WebCore::CSSParser::parseSystemFont

I assume it does some fopen() and chokes on when looking for sans-serif 
replacement.

Can you run the application with truss? We should see the fopen() and 
shortly after the crash. Upload the truss output.

[1] http://fonts.googleapis.com/css?family=Droid+Sans:400,700

Michael