Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
Thanks for the feedback. Not sure yet but am able to get application stack traces on pure c++ application but not Qt though. On Fri, Aug 4, 2023 at 1:03 AM Thiago Macieira wrote: > On Thursday, 3 August 2023 09:21:26 PDT Ramakanth Kesireddy wrote: > > Thanks for the inputs. It helped to resolve the issue. Hope these asserts > > are enabled only in Qt debug build as app is able to run fine on Qt > 5.15.8 > > enterprise installer version. > > Internal assertions are only enabled in debug builds. > > In release builds, they are simply assumed. You must still obey them, > whether > they got printed or not. So, no, your app is *not* able to run fine. It > still > has a race condition that only happened to cause no visible effect for you > (yet). > > > However, the application stack traces are not seen when used with massif > > tool even after enabling config+=debug and QMAKE_CXXFLAGS_DEBUG += -g. > > > > Am I missing something so that application debug symbols are being read > and > > shown as stack trace on exit of application? > > Sorry, that's a Massif question now. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Cloud Software Architect - Intel DCAI Cloud Engineering > ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
On Thursday, 3 August 2023 09:21:26 PDT Ramakanth Kesireddy wrote: > Thanks for the inputs. It helped to resolve the issue. Hope these asserts > are enabled only in Qt debug build as app is able to run fine on Qt 5.15.8 > enterprise installer version. Internal assertions are only enabled in debug builds. In release builds, they are simply assumed. You must still obey them, whether they got printed or not. So, no, your app is *not* able to run fine. It still has a race condition that only happened to cause no visible effect for you (yet). > However, the application stack traces are not seen when used with massif > tool even after enabling config+=debug and QMAKE_CXXFLAGS_DEBUG += -g. > > Am I missing something so that application debug symbols are being read and > shown as stack trace on exit of application? Sorry, that's a Massif question now. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
Thanks for the inputs. It helped to resolve the issue. Hope these asserts are enabled only in Qt debug build as app is able to run fine on Qt 5.15.8 enterprise installer version. However, the application stack traces are not seen when used with massif tool even after enabling config+=debug and QMAKE_CXXFLAGS_DEBUG += -g. Am I missing something so that application debug symbols are being read and shown as stack trace on exit of application? Appreciate any inputs in this regard. Best Regards, Ramakanth On Wed, Aug 2, 2023 at 10:42 PM Thiago Macieira wrote: > On Wednesday, 2 August 2023 09:46:54 PDT Ramakanth Kesireddy wrote: > > ok..Does it mean installTranslator() is not invoked in the main thread? > > That's what your backtrace says: > > > #9 0x75f8966e in QCoreApplication::installTranslator > > (translationFile=) at kernel/qcoreapplication.cpp:2078 > > #10 0x5562c654 in Translator::loadLanguage (this=0x7fffde80, > > langId=0) at translator.cpp:89 > > #11 0x5562c00e in Translator::installTranslator > > (this=0x7fffde80) at translator.cpp:15 > ... > > #14 0x75d60b0f in QThreadPoolThread::run (this=0x55f73320) at > > thread/qthreadpool.cpp:100 > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Cloud Software Architect - Intel DCAI Cloud Engineering > ___ > 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
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
On Wednesday, 2 August 2023 09:46:54 PDT Ramakanth Kesireddy wrote: > ok..Does it mean installTranslator() is not invoked in the main thread? That's what your backtrace says: > #9 0x75f8966e in QCoreApplication::installTranslator > (translationFile=) at kernel/qcoreapplication.cpp:2078 > #10 0x5562c654 in Translator::loadLanguage (this=0x7fffde80, > langId=0) at translator.cpp:89 > #11 0x5562c00e in Translator::installTranslator > (this=0x7fffde80) at translator.cpp:15 ... > #14 0x75d60b0f in QThreadPoolThread::run (this=0x55f73320) at > thread/qthreadpool.cpp:100 -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
ok..Does it mean installTranslator() is not invoked in the main thread? Thanks and Regards, Ramakanth On Wed, Aug 2, 2023 at 9:17 PM Thiago Macieira wrote: > On Tuesday, 1 August 2023 21:54:47 PDT Ramakanth Kesireddy wrote: > > Am unable to locate core dump even after setting ulimit -c unlimited. > > It was probably captured by systemd-coredumpd. You can find it with > coredumpctl. > > > #4 0x75d4a852 in qt_assert_x (where=where@entry=0x7618ff5b > > "QCoreApplication::sendEvent", what=, > > file=file@entry=0x7618ff00 "kernel/qcoreapplication.cpp", > > line=line@entry=553) at > > ../../include/QtCore/../../src/corelib/global/qlogging.h:90 > > #5 0x75f80061 in QCoreApplicationPrivate::checkReceiverThread > > (receiver=receiver@entry=0x7fffddf0) > > at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208 > [cut] > > #16 0x75c70609 in start_thread (arg=) at > > pthread_create.c:477 > > #17 0x75847133 in clone () at > > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > The assertion is correct. You didn't run this in the main() thread. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Cloud Software Architect - Intel DCAI Cloud Engineering > ___ > 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
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
On Tuesday, 1 August 2023 21:54:47 PDT Ramakanth Kesireddy wrote: > Am unable to locate core dump even after setting ulimit -c unlimited. It was probably captured by systemd-coredumpd. You can find it with coredumpctl. > #4 0x75d4a852 in qt_assert_x (where=where@entry=0x7618ff5b > "QCoreApplication::sendEvent", what=, > file=file@entry=0x7618ff00 "kernel/qcoreapplication.cpp", > line=line@entry=553) at > ../../include/QtCore/../../src/corelib/global/qlogging.h:90 > #5 0x75f80061 in QCoreApplicationPrivate::checkReceiverThread > (receiver=receiver@entry=0x7fffddf0) > at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208 [cut] > #16 0x75c70609 in start_thread (arg=) at > pthread_create.c:477 > #17 0x75847133 in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 The assertion is correct. You didn't run this in the main() thread. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
Am unable to locate core dump even after setting ulimit -c unlimited. Not sure if there is any system configuration in ubuntu 20.04 or application which doesnot allows to generate coredump file. Shall try to run on another ubuntu 20.04 if it makes any difference. However, when I run the application with gdb, below are the traces: ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread. Current thread 0x0x55f73320. Receiver '' (of type 'QApplication') was created in thread 0x0x55ed0f20", file kernel/qcoreapplication.cpp, line 553 Thread 4 "Thread (pooled)" received signal SIGABRT, Aborted. [Switching to Thread 0x72000700 (LWP 4347)] __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7574a859 in __GI_abort () at abort.c:79 #2 0x75d508ee in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #3 0x75d51615 in QMessageLogger::fatal (this=this@entry=0x71fff990, msg=msg@entry=0x76099018 "ASSERT failure in %s: \"%s\", file %s, line %d") at global/qlogging.cpp:893 #4 0x75d4a852 in qt_assert_x (where=where@entry=0x7618ff5b "QCoreApplication::sendEvent", what=, file=file@entry=0x7618ff00 "kernel/qcoreapplication.cpp", line=line@entry=553) at ../../include/QtCore/../../src/corelib/global/qlogging.h:90 #5 0x75f80061 in QCoreApplicationPrivate::checkReceiverThread (receiver=receiver@entry=0x7fffddf0) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208 #6 0x771e2f20 in QApplication::notify (this=0x7fffddf0, receiver=0x7fffddf0, e=0x71fffc50) at kernel/qapplication.cpp:2878 #7 0x75f807d1 in QCoreApplication::notifyInternal2 (receiver=0x7fffddf0, event=0x71fffc50) at kernel/qcoreapplication.cpp:1064 #8 0x75f80a0a in QCoreApplication::sendEvent (receiver=, event=event@entry=0x71fffc50) at kernel/qcoreapplication.cpp:1462 #9 0x75f8966e in QCoreApplication::installTranslator (translationFile=) at kernel/qcoreapplication.cpp:2078 #10 0x5562c654 in Translator::loadLanguage (this=0x7fffde80, langId=0) at translator.cpp:89 #11 0x5562c00e in Translator::installTranslator (this=0x7fffde80) at translator.cpp:15 #12 0x5562ca30 in QtConcurrent::VoidStoredMemberFunctionPointerCall0::runFunctor (this=0x55f5b940) at ../../../install/qt5.15.8/include/QtConcurrent/qtconcurrentstoredfunctioncall.h:205 #13 0x555cbfa5 in QtConcurrent::RunFunctionTask::run (this=0x55f5b940) at ../../../install/qt5.15.8/include/QtConcurrent/qtconcurrentrunbase.h:136 #14 0x75d60b0f in QThreadPoolThread::run (this=0x55f73320) at thread/qthreadpool.cpp:100 #15 0x75d5c589 in QThreadPrivate::start (arg=0x55f73320) at thread/qthread_unix.cpp:331 #16 0x75c70609 in start_thread (arg=) at pthread_create.c:477 #17 0x75847133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 On Mon, Jul 31, 2023 at 8:59 PM Thiago Macieira wrote: > On Sunday, 30 July 2023 10:11:55 PDT Ramakanth Kesireddy wrote: > > QCoreApplication::installTranslator(). > > ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to > > objects owned by a different thread. Current thread 0x0x55a25cfacea0. > > Receiver '' (of type 'QApplication') was created in thread > > 0x0x55a25cf32ef0", file kernel/qcoreapplication.cpp, line 553 > > Aborted (core dumped) > > > > Can anyone let me know if there is any issue with the below configure > line > > which causes the assert error on ubuntu 20.04 with Qt 5.15.8? > > No, nothing obvious. It could be a mismatch of having two different Qt > loaded > into memory at the same time. Can you provide the stack trace of this > warning? > It says "core dumped" so it means you have a core dump to get the trace > from. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Cloud Software Architect - Intel DCAI Cloud Engineering > ___ > 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
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
On Sunday, 30 July 2023 10:11:55 PDT Ramakanth Kesireddy wrote: > QCoreApplication::installTranslator(). > ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to > objects owned by a different thread. Current thread 0x0x55a25cfacea0. > Receiver '' (of type 'QApplication') was created in thread > 0x0x55a25cf32ef0", file kernel/qcoreapplication.cpp, line 553 > Aborted (core dumped) > > Can anyone let me know if there is any issue with the below configure line > which causes the assert error on ubuntu 20.04 with Qt 5.15.8? No, nothing obvious. It could be a mismatch of having two different Qt loaded into memory at the same time. Can you provide the stack trace of this warning? It says "core dumped" so it means you have a core dump to get the trace from. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
Though am able to get application stack traces while running in debug mode with Qt(debug) and massif, it aborts the application while launching app. It does works fine when used with Qt 5.15 online commercial installer. QCoreApplication::installTranslator(). ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread. Current thread 0x0x55a25cfacea0. Receiver '' (of type 'QApplication') was created in thread 0x0x55a25cf32ef0", file kernel/qcoreapplication.cpp, line 553 Aborted (core dumped) Can anyone let me know if there is any issue with the below configure line which causes the assert error on ubuntu 20.04 with Qt 5.15.8? ./configure -commercial -confirm-license -debug -prefix /home/install/target/qt5.15.8 -bundled-xcb-xinput -skip qt3d -skip qtactiveqt -skip qtandroidextras -skip qtcanvas3d -skip qtconnectivity \ -skip qtlocation -skip qtlottie -skip qtpurchasing -skip qtscxml -skip qtspeech -skip qtmultimedia -skip qtscript -skip qtserialbus -skip qtsensors -skip qtwebglplugin -skip qtdatavis3d \ -skip qtgamepad -skip qtquick3d -skip qtquicktimeline -skip qtwayland -skip qtwebsockets -skip qtwebview -skip qtwebengine -skip qtwebchannel -skip qtwinextras \ -skip qtx11extras -skip qtmacextras -skip qtxmlpatterns -skip qtsvg -nomake tools -nomake tests -nomake examples -no-compile-examples -reduce-exports -no-use-gold-linker -no-iconv -no-harfbuzz \ -skip qtandroidextras -skip qtnetworkauth -no-openssl -no-pch -no-zlib -qt-libjpeg -qt-libpng -system-sqlite -feature-accessibility -v Best Regards, Ramakanth On Wed, Jul 26, 2023 at 12:31 AM Thiago Macieira wrote: > On Tuesday, 25 July 2023 10:38:28 PDT Ramakanth Kesireddy wrote: > > In the massif_report.txt, no application stack traces are seen. > > > > Please let me know if am missing anything in this regard. > > Why do you think this is a Qt problem? Do you get the stack traces for > non-Qt > applications? How were those applications built? > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Cloud Software Architect - Intel DCAI Cloud Engineering > ___ > 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
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
On Wednesday, 26 July 2023 02:09:48 PDT Ramakanth Kesireddy wrote: > Yes I am able to get the stack traces for non-Qt applications using g++ > like g++ -g -o my_app main.cpp. > However, when I build the Qt application with Qt creator, it > doesnot outputs the application trace. > > Do I need to build with qmake config+=debug on command line to generate > application stack trace? Please paste the g++ command-line that qmake generated and make printed for your project. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
Yes I am able to get the stack traces for non-Qt applications using g++ like g++ -g -o my_app main.cpp. However, when I build the Qt application with Qt creator, it doesnot outputs the application trace. Do I need to build with qmake config+=debug on command line to generate application stack trace? Thanks for your inputs. On Wed, Jul 26, 2023 at 12:31 AM Thiago Macieira wrote: > On Tuesday, 25 July 2023 10:38:28 PDT Ramakanth Kesireddy wrote: > > In the massif_report.txt, no application stack traces are seen. > > > > Please let me know if am missing anything in this regard. > > Why do you think this is a Qt problem? Do you get the stack traces for > non-Qt > applications? How were those applications built? > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Cloud Software Architect - Intel DCAI Cloud Engineering > ___ > 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
Re: [Interest] Application stack traces are not seen using Massif with Qt debug symbols
On Tuesday, 25 July 2023 10:38:28 PDT Ramakanth Kesireddy wrote: > In the massif_report.txt, no application stack traces are seen. > > Please let me know if am missing anything in this regard. Why do you think this is a Qt problem? Do you get the stack traces for non-Qt applications? How were those applications built? -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
