indeed that was the issue! for those just tuning in, calling "windeployqt" with the "--pdb" option did the trick.
-dave > On Oct 25, 2021, at 1:37 AM, Alexandru Croitor <alexandru.croi...@qt.io> > wrote: > > Hi, > > From the 'bad' screenshot, it appears that the .pdb files are not picked up. > Source mappings don't affect lookup of pdb files as far as i i know. > If you mouse hover over one of the gray QFileInfo rows, what does the > QtCreator popup say? > > Perhaps when you run your application, you've already copied some of the Qt > dlls into the app dir (or some other dir and adjusted PATH), but did not copy > the pdbs to the same location as well? > >> On 24. Oct 2021, at 23:36, David M. Cotter <d...@kjams.com> wrote: >> >> i'm on Windows >> debugging a Qt 6.2 app >> >> when using an example project, debugging into source works fine. >> if i pause the app, the call stack is correct: >> >> <good.png> >> >> >> however, when using my project however (which is monumental, and very >> custom), call stack of Qt source is all wrong.. >> >> .<bad.png> >> >> note i have the same source path mappings for both projects: >> >> <src.png> >> >> what part(s) of my project config or .pro file could possibly cause these >> symptoms? >> >> thanks >> >> -dave >> >> ps: free Karaoke software goes to the person who can solve this! >> >> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org >> https://lists.qt-project.org/listinfo/interest > _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
