can't debug hand-built Qt Frameworks

davecotter · wrote on 1 Jul 2021, 18:47

okay, so after some more testing i see that i CAN in fact, now debug, and set breakpoints within the Qt code base. This is true even though i do not see any ".dSYM" files.

so this question is answered. thanks so much for your help. :D

not sure why QHelpGenerator failed to build, or what the consequences are, if any. if you have any ideas on that please let me know.

(also i apologize if helping me was frustrating, i'm doing my best and sometimes i have a hard time understanding stuff. but seems i got it in the end.)

SGaist · wrote on 2 Jul 2021, 18:57

AFAIR (but might be wrong), the .dSYM file are generated when you do a "release with debug symbol" build.

I do not know for QHelpGenerator, the failure source is upper in the build log.

Glad you can debug as you wish :-)

davecotter · wrote on 2 Jul 2021, 19:03

and how does one do a "release with debug symbols" build?

SGaist · wrote on 2 Jul 2021, 19:07

If memory serves well, something like "-release -force-debug-info".

davecotter · wrote on 2 Jul 2021, 20:38

if i do -release does that mean i do NOT do -debug-and-release? ie: are they mutually exclusive?

SGaist · wrote on 4 Jul 2021, 19:36

I do not remember which one takes precedents over the other. You can try to mix debug-and-release with force-bebug-info.

davecotter · 7 Apr 2021, 20:09

My final commands were:

cd /Volumes/Developer/depot/Qt5_Source
git clone git://code.qt.io/qt/qt5.git
mv ./qt5 ./Src
cd Src
git checkout 5.15.2
perl init-repository --module-subset=default,-qtwebengine,-qt3d,-qtcharts,-qtquick3d,-qtquickcontrols,-qtquickcontrols2,-qtquicktimeline
cd ..
mkdir build
cd build
../Src/configure -prefix ../clang_64 -force-debug-info -separate-debug-info -debug-and-release -opensource -nomake examples -nomake tests -confirm-license
make -j12
make -j1 install

no errors, and i had separate debug .dSYM files. haven't tested release yet.

By the way it took almost a week, half a dozen web pages, and almost two dozen back-and-forth replies in the forums to arrive at the above formula.

The fact that there is no such example just posted on the documentation web site is just stunning to me.

:)

davecotter · 7 Apr 2021, 22:25

i take it back. now, all i did was change two strings in one file:
in the file avfvideorenderercontrol.mm i changed line 273 to read:

qWarning("Failed to activate video surface (OpenGL)");

and changed line 298 to read:

qWarning("Failed to activate video surface (QImage)");

Previously, they both had the same warning, so you could not know which one was hit by just seeing the console output.

then, i tried to compile that one module:

cd /Volumes/Developer/depot/Qt5_Source/build/qtmultimedia/src/plugins/avfoundation
make -j12
make install

and it SEEMED to do SOMETHING, no errors.
but now when i run my app, i can't make ANY breakpoints resolve, and the warning, when fired, does NOT contain my updated string.

i even then tried to make then make install from the root, but same problem: breakpoints don't resolve, can't debug into Qt frameworks :(

just FYI i have edited my kit->environment to have this line:

DYLD_IMAGE_SUFFIX=_debug

but that didn't help

SGaist · wrote on 5 Jul 2021, 19:28

Is this your developer build ? If so there's no need to call make install.

davecotter · wrote on 6 Jul 2021, 15:13

okay but is there a reason i should NOT call make install? i did make install the first time, when debugging DID work fine. it only stopped after i modified a file. does calling make install break something? besides i was under the impression i was building both debug and release?

SGaist · wrote on 6 Jul 2021, 18:58

AFAIK, it should not.

Did you try to do a clean rebuild ?