[Development] debug symbols for official Qt releases

Jędrzej Nowacki jedrzej.nowacki at theqtcompany.com
Fri Mar 4 13:08:08 CET 2016

On Wednesday 02 of March 2016 09:00:35 Gunnar Roth wrote:
> >On 2016-03-01, Milian Wolff <milian.wolff at kdab.com> wrote:
> >> b) Apparently there are never any debug symbols shipped for the release
> >> build fo Qt. Having debug symbols even for a release build is crucial
> >> for a good profiling experience. Could we maybe get release builds in
> >> the future with - force-debug-info to improve this situation? I'm aware
> >> that one can get some sense out of a profiler when only the end-level
> >> application is build in that way, but one can often get much more
> >> insight when the stack below (or even in- between for the eventloop and
> >> signal/slot magic) also gets annotated stack frames. Right now, I have
> >> to suggest people to build Qt themselves for the sole purpose of
> >> profiling... A pity!
> >
> >This would be amazing. Also for getting better backtraces from crashes
> >at users systems.
> I normally use release build always even for debugging. It were also nice if
> Qt would set the enhanced pdb option to get better release debugging
> experience, /d2Zi+ option for vs2012 and /Zo for Vs2013 upd3 and VS2015.
> As i have other reasons to always build Qt myself and maintain patches
> others than these, i have no real problem with the current state, but would
> still be glad if pdb for release are build and delivered with the enhanced
> pdb option.
> Regards,
> Gunnar Roth

This is related:

The option is being evaluated. The main problem is that it seems that the 
installer size grows 2x with force-debug-info enabled, we need to confirm that 
it is not the case.


More information about the Development mailing list