Question about debugging info for AppImage and Snap

[Boudewijn Rempt]

On Fri, 17 Jun 2016, Dmitry Kazakov wrote:

> Hi, all!
> 
> Recently I got quite a few requests about Krita hanging-up on Ubuntu 14.04.
> Ane the biggest problem for me is that I cannot get a proper backtrace from
> the users. And what is more, if I decide to reproduce the bug in a virtual
> machine, I will have to build Krita and most of the dependencies (Qt + KF5)
> myself manually, which is from 3 to 4 hours of my work. If we need to build
> everything on each type of the supported system just for the sake of
> reproducing a bug, it is really a waste of time... So I have a few
> questions:
> 
> 1) Is it possible to produce a separate debugging info package for the
> AppImage package somehow?

Not that I know.

> 2) If not, why don't we build a dbg-enabled version of the package? I don't
> think it is too difficult. It might be done from the same build tree from
> the same script, just skipping/packaging before the stripping phase. Can we
> correct our scripts to produce that?

Yes, that's possible. The package would be really big, and files.kde.org is
already groaning under the strain of all the packages we do, so I would do
this for specific investigations instead of as a matter of course. 

I haven't tried getting a backtrace from a package with debug symbols yet.

> 3) What is the status of debugging info for the snap packages? Do they
> support that? If yes can we use them for testing the bugreports?

No idea at all. Well, that's not quite true. I know that snap got a lot of
flak because their libreoffice snap was soooooo big, but that included the
debug symbols, too: http://lwn.net/Articles/691309/#Comments

I'm not sure where that's done though. I can make a krita/3.0 branch debug 
appimage today.
-- 
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org