[Interest] Application stack traces are not seen using Massif with Qt debug symbols

[Ramakanth Kesireddy]

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 0x0x555555f73320.
Receiver '' (of type 'QApplication') was created in thread
0x0x555555ed0f20", file kernel/qcoreapplication.cpp, line 553

Thread 4 "Thread (pooled)" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffff2000700 (LWP 4347)]
__GI_raise (sig=sig at 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 at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff574a859 in __GI_abort () at abort.c:79
#2  0x00007ffff5d508ee in qt_message_fatal (context=..., message=...) at
global/qlogging.cpp:1914
#3  0x00007ffff5d51615 in QMessageLogger::fatal
(this=this at entry=0x7ffff1fff990,

    msg=msg at entry=0x7ffff6099018 "ASSERT failure in %s: \"%s\", file %s,
line %d") at global/qlogging.cpp:893
#4  0x00007ffff5d4a852 in qt_assert_x (where=where at entry=0x7ffff618ff5b
"QCoreApplication::sendEvent", what=<optimized out>,
    file=file at entry=0x7ffff618ff00 "kernel/qcoreapplication.cpp",
line=line at entry=553) at
../../include/QtCore/../../src/corelib/global/qlogging.h:90
#5  0x00007ffff5f80061 in QCoreApplicationPrivate::checkReceiverThread
(receiver=receiver at entry=0x7fffffffddf0)
    at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208
#6  0x00007ffff71e2f20 in QApplication::notify (this=0x7fffffffddf0,
receiver=0x7fffffffddf0, e=0x7ffff1fffc50) at kernel/qapplication.cpp:2878
#7  0x00007ffff5f807d1 in QCoreApplication::notifyInternal2
(receiver=0x7fffffffddf0, event=0x7ffff1fffc50) at
kernel/qcoreapplication.cpp:1064
#8  0x00007ffff5f80a0a in QCoreApplication::sendEvent (receiver=<optimized
out>, event=event at entry=0x7ffff1fffc50) at kernel/qcoreapplication.cpp:1462
#9  0x00007ffff5f8966e in QCoreApplication::installTranslator
(translationFile=<optimized out>) at kernel/qcoreapplication.cpp:2078
#10 0x000055555562c654 in Translator::loadLanguage (this=0x7fffffffde80,
langId=0) at translator.cpp:89
#11 0x000055555562c00e in Translator::installTranslator
(this=0x7fffffffde80) at translator.cpp:15
#12 0x000055555562ca30 in
QtConcurrent::VoidStoredMemberFunctionPointerCall0<void,
Translator>::runFunctor (this=0x555555f5b940)
    at
../../../install/qt5.15.8/include/QtConcurrent/qtconcurrentstoredfunctioncall.h:205
#13 0x00005555555cbfa5 in QtConcurrent::RunFunctionTask<void>::run
(this=0x555555f5b940)
    at
../../../install/qt5.15.8/include/QtConcurrent/qtconcurrentrunbase.h:136
#14 0x00007ffff5d60b0f in QThreadPoolThread::run (this=0x555555f73320) at
thread/qthreadpool.cpp:100
#15 0x00007ffff5d5c589 in QThreadPrivate::start (arg=0x555555f73320) at
thread/qthread_unix.cpp:331
#16 0x00007ffff5c70609 in start_thread (arg=<optimized out>) at
pthread_create.c:477
#17 0x00007ffff5847133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

On Mon, Jul 31, 2023 at 8:59 PM Thiago Macieira <thiago.macieira at intel.com>
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 at qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20230802/7daa402b/attachment.htm>