https://bugs.kde.org/show_bug.cgi?id=492886

--- Comment #5 from localtoast <ipsum.te.fu...@gmail.com> ---
(In reply to Sam James from comment #4)
> That Valgrind issue looks like a bug in Valgrind, see
> https://bugs.kde.org/show_bug.cgi?id=381819. You can try the patch there or
> just try ASAN and UBSAN instead.

Thanks for the direction. I patched valgrind and ran again. Still got exactly
the same error, but also some output which might be more relevant:


==1135== Memcheck, a memory error detector
==1135== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==1135== Using Valgrind-3.23.1.GIT and LibVEX; rerun with -h for copyright info
==1135== Command: plasmashell
==1135== 
Detected locale "en_US.iso88591" with character encoding "ISO-8859-1", which is
not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "en_US.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
==1135== Syscall param writev(vector[0]) points to uninitialised byte(s)
==1135==    at 0x76A59DF: writev (in /usr/lib64/libc.so.6)
==1135==    by 0x4BF3702: ??? (in /usr/lib64/libxcb.so.1.1.0)
==1135==    by 0x4BF3F70: ??? (in /usr/lib64/libxcb.so.1.1.0)
==1135==    by 0x4BF5574: ??? (in /usr/lib64/libxcb.so.1.1.0)
==1135==    by 0x4BF55EE: xcb_wait_for_reply (in /usr/lib64/libxcb.so.1.1.0)
==1135==    by 0xD8BA5D2:
QXcbConnection::initializeScreensFromMonitor(xcb_screen_iterator_t*, int,
QXcbScreen**, bool) (qxcbconnection_screens.cpp:501)
==1135==    by 0xD8BBCD7: QXcbConnection::initializeScreens(bool)
(qxcbconnection_screens.cpp:317)
==1135==    by 0xD8B3018: QXcbConnection::QXcbConnection(QXcbNativeInterface*,
bool, unsigned int, char const*) (qxcbconnection.cpp:72)
==1135==    by 0xD8D600D: QXcbIntegration::QXcbIntegration(QList<QString>
const&, int&, char**) (qxcbintegration.cpp:170)
==1135==    by 0x48584E7: QXcbIntegrationPlugin::create(QString const&,
QList<QString> const&, int&, char**) (qxcbmain.cpp:22)
==1135==    by 0x66F46B7: init_platform(QString const&, QString const&, QString
const&, int&, char**) (qguiapplication.cpp:1249)
==1135==    by 0x66F760F: QGuiApplicationPrivate::createPlatformIntegration()
(qguiapplication.cpp:1533)
==1135==  Address 0xcf5c115 is 4,533 bytes inside a block of size 21,176
alloc'd
==1135==    at 0x4847B6B: calloc (vg_replace_malloc.c:1675)
==1135==    by 0x4BF30DF: xcb_connect_to_fd (in /usr/lib64/libxcb.so.1.1.0)
==1135==    by 0x4BF7BC8: xcb_connect_to_display_with_auth_info (in
/usr/lib64/libxcb.so.1.1.0)
==1135==    by 0x8218699: _XConnectXCB (in /usr/lib64/libX11.so.6.4.0)
==1135==    by 0x8209288: XOpenDisplay (in /usr/lib64/libX11.so.6.4.0)
==1135==    by 0xD8B7D92: QXcbBasicConnection::QXcbBasicConnection(char const*)
(qxcbconnection_basic.cpp:77)
==1135==    by 0xD8B2E13: QXcbConnection::QXcbConnection(QXcbNativeInterface*,
bool, unsigned int, char const*) (qxcbconnection.cpp:62)
==1135==    by 0xD8D600D: QXcbIntegration::QXcbIntegration(QList<QString>
const&, int&, char**) (qxcbintegration.cpp:170)
==1135==    by 0x48584E7: QXcbIntegrationPlugin::create(QString const&,
QList<QString> const&, int&, char**) (qxcbmain.cpp:22)
==1135==    by 0x66F46B7: init_platform(QString const&, QString const&, QString
const&, int&, char**) (qguiapplication.cpp:1249)
==1135==    by 0x66F760F: QGuiApplicationPrivate::createPlatformIntegration()
(qguiapplication.cpp:1533)
==1135==    by 0x66F81E7: QGuiApplicationPrivate::createEventDispatcher()
(qguiapplication.cpp:1552)
==1135==  Uninitialised value was created by a stack allocation
==1135==    at 0xD8A2510: ??? (in /usr/lib64/libQt6XcbQpa.so.6.7.2)
==1135== 
vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x70 0xA2 0xC3 0x0 0xC5
0xFB 0x11 0x83
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x1 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==1135== valgrind: Unrecognised instruction at address 0x6742559.
==1135==    at 0x6742559: QScreen::QScreen(QPlatformScreen*) (qscreen.cpp:53)
==1135==    by 0x675A218:
QWindowSystemInterface::handleScreenAdded(QPlatformScreen*, bool)
(qwindowsysteminterface.cpp:716)
==1135==    by 0xD8BBDEF: QXcbConnection::initializeScreens(bool)
(qxcbconnection_screens.cpp:347)
==1135==    by 0xD8B3018: QXcbConnection::QXcbConnection(QXcbNativeInterface*,
bool, unsigned int, char const*) (qxcbconnection.cpp:72)
==1135==    by 0xD8D600D: QXcbIntegration::QXcbIntegration(QList<QString>
const&, int&, char**) (qxcbintegration.cpp:170)
==1135==    by 0x48584E7: QXcbIntegrationPlugin::create(QString const&,
QList<QString> const&, int&, char**) (qxcbmain.cpp:22)
==1135==    by 0x66F46B7: init_platform(QString const&, QString const&, QString
const&, int&, char**) (qguiapplication.cpp:1249)
==1135==    by 0x66F760F: QGuiApplicationPrivate::createPlatformIntegration()
(qguiapplication.cpp:1533)
==1135==    by 0x66F81E7: QGuiApplicationPrivate::createEventDispatcher()
(qguiapplication.cpp:1552)
==1135==    by 0x70A7E5D: QCoreApplicationPrivate::init()
(qcoreapplication.cpp:905)
==1135==    by 0x66FA86F: QGuiApplicationPrivate::init()
(qguiapplication.cpp:1580)
==1135==    by 0x52FF4CC: QApplicationPrivate::init() (qapplication.cpp:472)
==1135== Your program just tried to execute an instruction that Valgrind
==1135== did not recognise.  There are two possible reasons for this.
==1135== 1. Your program has a bug and erroneously jumped to a non-code
==1135==    location.  If you are running Memcheck and you just saw a
==1135==    warning about a bad jump, it's probably your program's fault.
==1135== 2. The instruction is legitimate but Valgrind doesn't handle it,
==1135==    i.e. it's Valgrind's fault.  If you think this is the case or
==1135==    you are not sure, please let us know and we'll try to fix it.
==1135== Either way, Valgrind will now raise a SIGILL signal which will
==1135== probably kill your program.
==1135== 
==1135== Process terminating with default action of signal 4 (SIGILL)
==1135==  Illegal opcode at address 0x6742559
==1135==    at 0x6742559: QScreen::QScreen(QPlatformScreen*) (qscreen.cpp:53)
==1135==    by 0x675A218:
QWindowSystemInterface::handleScreenAdded(QPlatformScreen*, bool)
(qwindowsysteminterface.cpp:716)
==1135==    by 0xD8BBDEF: QXcbConnection::initializeScreens(bool)
(qxcbconnection_screens.cpp:347)
==1135==    by 0xD8B3018: QXcbConnection::QXcbConnection(QXcbNativeInterface*,
bool, unsigned int, char const*) (qxcbconnection.cpp:72)
==1135==    by 0xD8D600D: QXcbIntegration::QXcbIntegration(QList<QString>
const&, int&, char**) (qxcbintegration.cpp:170)
==1135==    by 0x48584E7: QXcbIntegrationPlugin::create(QString const&,
QList<QString> const&, int&, char**) (qxcbmain.cpp:22)
==1135==    by 0x66F46B7: init_platform(QString const&, QString const&, QString
const&, int&, char**) (qguiapplication.cpp:1249)
==1135==    by 0x66F760F: QGuiApplicationPrivate::createPlatformIntegration()
(qguiapplication.cpp:1533)
==1135==    by 0x66F81E7: QGuiApplicationPrivate::createEventDispatcher()
(qguiapplication.cpp:1552)
==1135==    by 0x70A7E5D: QCoreApplicationPrivate::init()
(qcoreapplication.cpp:905)
==1135==    by 0x66FA86F: QGuiApplicationPrivate::init()
(qguiapplication.cpp:1580)
==1135==    by 0x52FF4CC: QApplicationPrivate::init() (qapplication.cpp:472)
==1135== 
==1135== HEAP SUMMARY:
==1135==     in use at exit: 465,768 bytes in 2,705 blocks
==1135==   total heap usage: 4,531 allocs, 1,826 frees, 723,348 bytes allocated
==1135== 
==1135== LEAK SUMMARY:
==1135==    definitely lost: 0 bytes in 0 blocks
==1135==    indirectly lost: 0 bytes in 0 blocks
==1135==      possibly lost: 3,520 bytes in 6 blocks
==1135==    still reachable: 460,232 bytes in 2,678 blocks
==1135==                       of which reachable via heuristic:
==1135==                         newarray           : 2,000 bytes in 14 blocks
==1135==         suppressed: 0 bytes in 0 blocks
==1135== Rerun with --leak-check=full to see details of leaked memory
==1135== 
==1135== For lists of detected and suppressed errors, rerun with: -s
==1135== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to