Re: Falkon in kdereview

2018-02-28 Thread Kevin Kofler
Adriaan de Groot wrote:
> That said, the FreeBSD CI VMs should have debug symbols, so we'll have to
> look at that since -- as you notice -- it makes the CI less useful for
> application developers.

QtWebEngine is special, it is built without debugging information for all 
the Chromium code by default. Make sure you build your QtWebEngine with: 
CONFIG += "webcore_debug v8base_debug force_debug_info"

This will build Chromium code with -g1 debuginfo. To get the normal -g2 (the 
default if you pass just -g, at least in GCC), you can try:
sed -i -e 's/symbol_level=1/symbol_level=2/g' src/core/config/common.pri
but this may cause the linker to run out of memory, and it can also crash 
other tools (e.g., the eu-strip tool that Fedora uses to split the debuginfo 
into a separate file crashes on it). So caveat emptor.

Another possibility is that the crash is in JITted code (e.g., JavaScript 
compiled by the V8 JIT), in which case you cannot possibly get a useful 
backtrace at all, no matter how much debugging information you enable.

Kevin Kofler



Falkon in kdereview

2018-02-28 Thread David Rosca
Hi,
I'd like to request review for Falkon.

It's been actually in kdereview for some time already, but I never got
to properly request review, sorry about that.

There is a project set up in bugzilla, CI build and code should be in
accordance with guidelines too.
There are also some autotests, although they are rather unstable on
FreeBSD build. It looks like crash in QtWebEngine, but the backtrace
from CI is without symbols, so it is unfortunately useless.

Target is Extragear for now, and later possibly moving to KDE Applications.

Thanks,
David


Re: Falkon in kdereview

2018-02-28 Thread Adriaan de Groot
On Wednesday, February 28, 2018 6:10:36 AM EST David Rosca wrote:
> There are also some autotests, although they are rather unstable on
> FreeBSD build. It looks like crash in QtWebEngine, but the backtrace
> from CI is without symbols, so it is unfortunately useless.

The KDE-FreeBSD developers are generally happy with *using* Qupzilla / Falkon 
though -- it's the autotests that fall over, not the browser itself. Something 
we'll have to look at by hand. Don't let it be a blocker.

That said, the FreeBSD CI VMs should have debug symbols, so we'll have to look 
at that since -- as you notice -- it makes the CI less useful for application 
developers.

[ade]


signature.asc
Description: This is a digitally signed message part.