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 resolv
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
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 QMAK
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
>
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 unlimite
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
>
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 applicatio
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
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::sen
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 bu
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 trac
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 th
Hi,
Am running Qt 5.15.8 debug version on desktop linux.
Below are steps used to enable application stack traces using massif and Qt
5.15.8.
1)Building Qt 5.15.8 in Debug Mode with below configure line:
./configure -commercial -confirm-license -debug -prefix
/home/install/qt5.15.8 -bundled-xcb-x
13 matches
Mail list logo
