Skip to content

Conversation

@yungyuc
Copy link
Member

@yungyuc yungyuc commented Dec 21, 2019

No description provided.

@yungyuc yungyuc changed the base branch from master to develop December 21, 2019 13:34
@yungyuc yungyuc self-assigned this Dec 21, 2019
@yungyuc yungyuc added the enhancement New feature or request label Dec 21, 2019
@yungyuc yungyuc merged commit 9b94eda into develop Dec 21, 2019
@yungyuc yungyuc deleted the feature/grid branch December 21, 2019 13:39
yungyuc pushed a commit that referenced this pull request Nov 24, 2022
yungyuc pushed a commit that referenced this pull request Nov 24, 2022
yungyuc added a commit that referenced this pull request Dec 7, 2022
…tion constructor

See https://doc.qt.io/qt-6/qapplication.html#QApplication .  The first argument argc needs to be a type int & and the object referenced needs to be available during the whole lifetime time of QApplication.

While macos and windows do not seem to crash, the Ubuntu Linux is particularly sensitive with the bug, and gets the following stacktrace:

Thread 1 "viewer" received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
65      ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
(gdb) where
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
#1  0x00007ffff7adb3f8 in std::char_traits<char>::length(char const*) (__s=0x2 <error: Cannot access memory at address 0x2>) at /opt/rh/gcc-toolset-10/root/usr/include/c++/10/bits/char_traits.h:371
#2  QByteArrayView::lengthHelperPointer<char>(char const*) (data=0x2 <error: Cannot access memory at address 0x2>) at /home/qt/work/qt/qtbase/src/corelib/text/qbytearrayview.h:144
#3  QByteArrayView::QByteArrayView<char*, true>(char* const&) (data=@0x555555943460: 0x2 <error: Cannot access memory at address 0x2>, this=<optimized out>) at /home/qt/work/qt/qtbase/src/corelib/text/qbytearrayview.h:188
#4  QCoreApplication::arguments() () at /home/qt/work/qt/qtbase/src/corelib/kernel/qcoreapplication.cpp:2498

It is similar to https://bugreports.qt.io/browse/QTBUG-59510, in which the root cause was pointed out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants