1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doc: Generalize info about -rdynamic to be not qmake specific

Browse Source 
Pick-to: 6.4
Fixes: QTBUG-88044
Change-Id: I079cb75b5a5c32e38dec73474c967cc836d94b68
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
This commit is contained in:
Kai Köhne 2022-08-18 15:15:04 +02:00
parent f9cd4a0290
commit 54e01d50f4
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/corelib/global/qlogging.cpp
View File

@ -2040,9 +2040,12 @@ void qErrnoWarning(int code, const char *msg, ...)
\row \li \c{%{backtrace [depth=N] [separator="..."]}} \li A backtrace with the number of frames \row \li \c{%{backtrace [depth=N] [separator="..."]}} \li A backtrace with the number of frames
specified by the optional \c depth parameter (defaults to 5), and separated by the optional specified by the optional \c depth parameter (defaults to 5), and separated by the optional
\c separator parameter (defaults to "|"). \c separator parameter (defaults to "|").
This expansion is available only on some platforms (currently only platfoms using glibc). This expansion is available only on some platforms (currently only platfoms using glibc).
Names are only known for exported functions. If you want to see the name of every function Names are only known for exported functions. If you want to see the name of every function
in your application, use \c{QMAKE_LFLAGS += -rdynamic}. in your application, make sure your application is compiled and linked with \c{-rdynamic},
or an equivalent of it.
When reading backtraces, take into account that frames might be missing due to inlining or When reading backtraces, take into account that frames might be missing due to inlining or
tail call optimization. tail call optimization.
\endtable \endtable