Isn't the issue that the debug symbols are not shipped in the first place? They usually reside in the object files, or are extracted into a dsym archive, and neither are shipped with the binary installation.
So placing the sources at the original compiled path won't really help. > On 21 Jan 2016, at 00:39, Mike Jackson <imikejack...@gmail.com> wrote: > >> >> On Jan 20, 2016, at 4:26 PM, Thiago Macieira <thiago.macie...@intel.com> >> wrote: >> >> On Wednesday 20 January 2016 09:50:51 Nils Jeisecke via Interest wrote: >>> On Tue, Jan 19, 2016 at 5:29 PM, Thiago Macieira >>> >>> <thiago.macie...@intel.com> wrote: >>>> Yes. Debug symbols in the pre-compiled builds do not work. >>> >>> Is this a known issue or shall I create a bug report? >> >> It's a known and, AFAIU, unfixable issue. That's just how the debug format >> stores the information. >> >> I think it should show line numbers, but it can't find the source code >> because >> you don't have the source code at the same place as the debugging >> information >> expects it to be. >> -- >> Thiago Macieira - thiago.macieira (AT) intel.com >> Software Architect - Intel Open Source Technology Center > > Not that I have tried this BUT in theory if you knew the exact paths that > Digia used to build the Qt distribution and set up your sources in the same > paths then the debug symbols might start working. At least that is the first > thing I would try. > > — > Mike Jackson > _______________________________________________ > Interest mailing list > Interest@qt-project.org <mailto:Interest@qt-project.org> > http://lists.qt-project.org/mailman/listinfo/interest > <http://lists.qt-project.org/mailman/listinfo/interest>
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
